Agents

An agent is a Markdown contract: runtime instructions plus tool allow-lists interpreted by an executor plugin. Coro swaps agents at phase boundaries so each step has a narrowly scoped mandate.

Below is the full roster shipped in base intelligence—not every agent joins every workflow, but recognition helps when reading logs.

Agent file	Role in one sentence
spec-writer	Turns tracker payloads into reviewer-ready specs the Planner can execute.
planner	Reads the repo after spec hand-off, detects language and risk, emits work items, and may reroute FAST vs STANDARD vs DEEP—or convert to campaigns.
analyzer	DEEP only — Produces authoritative design notes before decomposition when public surface or cross-cutting risk demands it.
coder	Implements planned work locally, invokes convention skills on demand, and opens PRs.
code-reviewer	Runs as a constrained sub-phase inside coding to sanity-check conventions, tests, and plan alignment—fast feedback before humans see the PR.
pr-reviewer	Merge gatekeeper: human SCM coordination, policy checks, iterative fix loops with the coder—then merge.
evaluator	Post-merge verifier: rebuilds/tests against merged commits, validates acceptance criteria, captures memory deltas and improvement proposals.
qa	DEEP lane enrichment after merge—extra testing rigour layered on evaluator outputs when the lane demands it.
campaign-architect	Campaign prelude — Captures shared architecture across many child repos/issues before decomposition.
campaign-planner	Fans out coordinated child jobs with explicit dependency and contract scaffolding.
campaign-integrator	Reconciles cross-child contracts and verifies integration checkpoints near the epic close.
campaign-evaluator	Aggregates campaign-level outcomes and surfaces systemic follow-ups.
memory-curator	The only subtractive memory editor—merges and compacts append-only memory safely under human review.

Text “diagram” of a typical STANDARD job

Tracker / CLI ──► spec-writer ──► planner ──► coder ⇄ code-reviewer
                                      │
                                      ▼ (PR open)
                                 pr-reviewer ⇄ humans
                                      │
                               merge / complete WI loop
                                      ▼
                                 evaluator ──► memory + proposals (optional paths)

Campaign flows insert architect → planner loop → per-child STANDARD/FAST/deep forks → integrator → campaign-evaluator. DEEP inserts analyzer before planning and activates QA after merge verification.

Exact YAML phase lists live beside each workflow file in the overlay you ship; when in doubt consult the workflow reference.

→ Agents reference tables