sr-subagent-driven-developmentlisted

# 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 - Tasks don't have tight coupling requiring shared state **vs. Executing Plans (parallel session):** - Same session (no context switch) - Fresh subagent per task (no context pollution) - Two-stage review after each task - Faster iteration (no human-in-loop between tasks) ## The Process 1. **Read plan, extract all tasks with full text, create todo list** 2. **Per task:** - Dispatch implementer subagent (see implementer-prompt.md) - If subagent asks questions, answer them before proceeding - Subagent implements, tests, commits, self-reviews - Dispatch spec reviewer subagent (see spec-reviewer-prompt.md) - If spec issues found, implementer fixes, re-review - Dispatch code quality reviewer subagent (see code-quality-reviewer-prompt.md) - If quality issues found, implementer fixes, re-review - Mark task complete 3. **After all tasks:** Dispatch final code reviewer for entire implementation 4. **Use sr-finishing-a-development-branch skill** ## Prompt Templates - `./implementer-prompt.md` - Dispatch implementer subagent - `./spec-reviewer-prompt.md` - Dispat