Reference — Agents
Each phase has a producing agent and an independent reviewer. The reviewer never edits the work: it issues a verdict before the phase transition.
| Usage order | Phase | Producing agent | Reviewer |
|---|---|---|---|
| 0 | (meta) | skraft-orchestrator | — |
| 1 | DISCOVER | backlog-discoverer | backlog-discoverer-reviewer |
| 2 | DISCUSS | backlog-planner | backlog-planner-reviewer |
| 3 | RESEARCH | solution-researcher | — |
| 4 | DESIGN | solution-architect | solution-architect-reviewer |
| 5 | DISTILL | acceptance-designer | acceptance-designer-reviewer |
| 6 | DELIVER | software-engineer | software-engineer-reviewer |
The orchestrator is the single entry point: it reads the state, dispatches the current phase agent, triggers the reviewer, applies the verdict (and retries), then moves on to the next phase.
Internal test-wiring workers (DELIVER phase)
In DELIVER, the software-engineer delegates test wiring to internal subagents
(user-invocable: false — not directly invocable). Each worker emits test wiring
only; the business TDD cycle stays with the software-engineer, who verifies the
worker in TIER-1 (RED → GREEN). A conditional fidelity lens joins the adversarial
review panel when the capability is active.
| Capability | Worker | Fidelity lens |
|---|---|---|
| Mocking (consumer) | mock-integration-worker | mock-fidelity-lens |
| Contract (provider) | contract-testing-worker | contract-fidelity-lens |