Subagent-Driven Development

Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.

Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration

When to Use

• Have an implementation plan with mostly independent tasks
• Want to stay in the current session (otherwise use executing-plans)
• See references/process-detail.md for decision tree and full process flow diagrams

The Process

1. Load plan — Read plan.md + manifest.json. Note task IDs and waves. Do NOT read briefing files into your context.
2. Dispatch per task — Send implementer a 2-3 sentence summary + briefing file path. Agent reads its own briefing from disk.
3. Two-stage review — Spec compliance first, then code quality. Both must pass before marking complete.
4. Wave boundaries — Re-read manifest.json to recover state after context compaction.