subagent-driven-developmentlisted

# Subagent-Driven Development Execute a plan in ONE session: dispatch a fresh implementer subagent per task → task review (spec + quality) after each → broad whole-branch review at the end. Upstream: <https://github.com/obra/superpowers>. Fresh-context briefs, fan-out width, and the per-task economy are governed by `[[parallel-subagent-economy]]`; when to decompose-and-fan-out at all by `[[monitor-orchestration]]`. This file covers only what is SDD-specific: the per-task implementer + two-stage review loop. ## Contents 1. When to use vs. alternatives 2. The per-task loop 3. Model selection 4. Handling implementer status 5. Constructing reviewer prompts 6. File handoffs + durable ledger 7. Red flags ## When to Use - Have a plan + tasks mostly independent + staying in THIS session → this skill. - Want a parallel session with human checkpoints → `superpowers:executing-plans` instead. - Tightly-coupled tasks or no plan → brainstorm/manual first. - Continuous execution: do not check in between tasks. Stop only on unresolvable BLOCKED, genuine ambiguity, or all-done. Narrate ≤1 line between tool calls — the ledger and tool results are the record. ## The Per-Task Loop 1. Read plan once; note global constraints; create todos + check the ledger (§6). 2. Pre-flight: scan the plan for tasks that contradict each other/the constraints, or that mandate something the rubric treats as a defect (test asserting nothing, verbatim-duplicated logic). Batch all findings to the human as one