subagent-driven-development

# Execute → Have an implementation plan with independent tasks? → **Fresh subagent per task + two-stage review.** 1. Read plan, extract all tasks, create TodoWrite 2. Per task: dispatch implementer → answer questions → implementer completes 3. Review stage 1 (spec compliance) → fix gaps → re-review until ✅ 4. Review stage 2 (code quality) → fix issues → re-review until ✅ 5. Mark complete, update checkpoint, drift check → next task → All tasks done: dispatch final code reviewer → finishing-a-development-branch. # 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. **Why subagents:** You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work. **Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration ## When to Use Use when you have a written implementation plan with mostly independent tasks and want to stay in the current session. For cross-session execution, use executing-plans instead. ## The Process 1. Read plan, extract all tasks with full text, create TodoWrite 2. Per task: dispatch implementer with task text + ba...