spawn-reviewers

Reviewer Fleet Dispatch (stage_20_spawn_reviewers)

This skill is the canonical reviewer-fleet dispatcher for /code-review at stage_20_spawn_reviewers. It is split out of commands/start.md so the orchestration spine stays lean; the orchestrator invokes it when the walker reaches stage_20_spawn_reviewers. The content below is authoritative for both MODE=local and MODE=github, with mode-specific Task scheduling: GitHub standard flow dispatches reviewers synchronously, while local standard flow preserves parallel background dispatch plus blocking collection.

The verifier fleet (stage_23) and the PLN-725 single-agent dispatch (stage_11 / stage_15) are not in this skill — they are owned by the code-review:verify-findings and code-review:singleton-dispatch skills respectively.

---

Reviewer Fleet (stage_20_spawn_reviewers)

This stage runs when the walker reaches stage_20.

PLN-725 Phase 8 — spawn-spec consumption (preferred path). Before walking the static tables below, Read <CR_DIR>/spawn.json (spec section). If the file exists and arbitrate_status != "fallback", dispatch one Task per entry in agents[], using the descriptor fields directly:

• agent_id → orchestrator-assigned ID; agent writes to <CR_DIR>/agent_{agent_id}.json.
• model → resolved per-agent model string (already accounts for BHA test-only routing and spawn.json.route overrides — do not re-derive).
• partitioned: true + partition_id → patches file is patches_p{partition_id}.txt; use the partition's files[] from partitions.json for <files_assigned>.
• partitioned: false → patches file is patches_all.txt; <files_assigned> is the full files_to_review list.
• subagent_type per descriptor: use code-review:code-review-worker-graph when reviewer ∈ {bug_hunter_b, impact, design_critic} (or the fast-path agent); use code-review:code-review-worker for every other descriptor. See the "Agent type" rule above. Pass the resolved GRAPH_PROJECT into the BHB / Impact / Design Critic / fast-path prompts.
• Prompt-suffix dispatch is two-level:
  • When source == "core", branch on the reviewer field to select the suffix: bug_hunter_a → BHA, bug_hunter_b → BHB, unified_auditor → Auditor, impact → Impact Analyzer, design_critic → Design Critic. (All five roles share source: "core", so source alone is not enough.) impact only appears in agents[] when invocation depth is deep AND signal extraction emitted exported_symbol_change or symbol_deletion; design_critic appears in agents[] on every deep review (an always-on conditional core reviewer). Both are graph-aware: impact and design_critic each load the codebase knowledge-graph protocol, so spawn both as code-review:code-review-worker-graph and substitute the resolved GRAPH_PROJECT into their suffixes.
  • When source is "rule" or "critic" → Domain Critic suffix (the reviewer field carries the critic name for the {critic_name} prompt slot). "rule" means the entry came from a deterministically matched critic-gates.json coverage[] rule (including migrated legacy moduleCritics[]); "critic" means the entry was LLM-proposed by coverage_critic. Both spawn as domain_<N> with sonnet.
  • When source == "fast_path" → Fast Path suffix (only emitted on the fast-path branch; mutually exclusive with the bucket walk).
• spec.fast_path: true → spec emits exactly one agent (agent_id: "fast"); skip the standard-flow tables and use the Fast Path suffix below.
• spec.gated_by_verify: true → a BLOCKING verify verdict from stage_15c fired (the canonical finding already lives in agent_coverage-verify-blocking.json). The spec has already been sanitized — only source: "core" agents will be present in agents[]; rule/critic-source reviewers were moved to skipped[] with reason: "gated_by_verify". Spawn the (sanitized) spec as-is and surface a one-line warning in the present step that arbitration was bypassed.
• spec.skipped[] → reviewers the spec deliberately did not spawn (e.g. test_quality deferred to PLN-723; bug_hunter_a skipped because all files cached). Do not re-add them.