← ClaudeAtlas

subagent-driven-developmentlisted

Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality).
mick-gsk/drift · ★ 14 · Code & Development · score 71
Install: claude install-skill mick-gsk/drift
# 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 - You have an implementation plan (from writing-plans skill) - Tasks are mostly independent - You want to stay in this session **vs. Executing Plans:** Same session, fresh context per task, faster iteration with no human-in-loop between tasks. ## The Process 1. **Read plan once** — extract all tasks with full text and context 2. **Create TodoWrite** with all tasks 3. **Per task:** - Dispatch implementer subagent with full task text + scene-setting context - Answer any questions before letting them proceed - Implementer implements, tests, commits, self-reviews - Dispatch **spec compliance reviewer** subagent - If spec issues found: implementer fixes → re-review - Dispatch **code quality reviewer** subagent - If quality issues found: implementer fixes → re-review - Mark task complete 4. After all tasks: dispatch final code reviewer for entire implementation 5. Use `superpowers:finishing-a-development-branch` ## Model Selection - **Mechanical tasks** (isolated functions, clear specs, 1-2 files): cheap/fast model - **Integration tasks** (multi-file, pattern matching, debugging): standard model - **Architecture/design/review**: most capable model ## H