subagent-driven-developmentlisted

# Subagent-Driven Development Dispatch fresh subagent per task with two-stage review after each. **Core principle:** Fresh subagent per task + two-stage review (spec then quality) + diff-based validation = high quality, fast iteration ## Quick Reference | Phase | Actor | Action | Exit Condition | |-------|-------|--------|----------------| | 1 | Controller | Read plan, extract tasks, capture BASE_SHA, create task list | All tasks tracked with BASE_SHA | | 2 | Subagent | Implement (templates/implementer.md) | Commit exists + tests pass + report includes HEAD_SHA | | 3 | Subagent | Spec review (templates/spec-reviewer.md) | Reviewer checked diff(BASE..HEAD) and returned ✅ or file:line issues | | 4 | Subagent | Quality review (templates/code-quality-reviewer.md) | Reviewer approved diff or returned severity-tagged issues | | 5 | Controller | Update state, mark complete, loop to step 2 | All tasks done | | 6 | Subagent | Final review of entire implementation | Approved | | 7 | Controller | Use finishing-a-development-branch | Branch complete | ## Task Contract Every task must satisfy these constraints: **Scope:** - One task = one commit (or tight commit stack) - No drive-by refactors; no formatting churn - No unrelated file changes **Verification:** - All tests pass (run full suite or affected subset) - Lint/typecheck pass (if applicable) - Commands actually executed (not assumed) **Report must include:** - BASE_SHA (from controller) - HEAD_SHA (after commit) - Commands