subagent-driven-developmentlisted

# Subagent-Driven Development Execute a written plan with fresh, narrowly briefed subagents where delegation pays for itself. Scale review to risk: low-risk tasks use focused tests and self-review, medium-risk work gets one independent boundary review, and high-risk work gets review at each risky boundary plus final independent verification. The default process executes tasks sequentially on one branch. Recursive coordinator mode is an explicit exception for independent tasks with disjoint ownership. **Why subagents:** each task gets deliberately fresh context that you construct. Some harnesses can inherit or fork parent history, so request a fresh context explicitly for implementers and reviewers. Hand each one exactly what its task needs, which keeps it focused and preserves your own context for coordination. **Git authorization:** selecting SDD never grants permission to commit, push, merge, or open a pull request. Preserve the user's and repository's existing authorization. When commits are authorized, the ledger records their ranges. Otherwise the ledger and working tree are the recovery mechanism. Recursive children never perform Git index or ref operations. **Continuous execution:** do not check in with your human partner between tasks. Stop only for a BLOCKED status you cannot resolve, ambiguity that prevents progress, or completion of all tasks. Narrate at most one short line between tool calls; the ledger and tool results carry the record. **Repository-wide ver