Subagent-Driven Development

Execute an implementation plan by dispatching one fresh subagent per task, each reviewed by a spec compliance reviewer and a code quality reviewer before the coordinator moves forward.

Why Fresh Subagents?

Each subagent receives only the context it needs — task description, relevant files, and acceptance criteria. It does not inherit the coordinator's full session history. This prevents context poisoning and keeps each task focused.

Coordinator Responsibilities

The coordinator:

1. Reads the full plan.md once
2. Dispatches subagents sequentially (or in parallel for independent tasks)
3. Reviews each task's output before proceeding
4. Patches failures without re-running the entire plan

Per-Task Execution Pattern

For each task in plan.md: