subagent-driven-development

Topics in the source

• Subagent-Driven Development
• When to Use
• The Process
• Setup
• Model Selection
• The Task Loop
• 1. Dispatch the implementer
• 2. Handle the report

Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality) after each, and a broad whole-branch review at the end. Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work. Core principle: Fresh subagent per task + task review (spec + quality) + broad final review = high quality, fast iteration Narration: between tool calls, narrate at most one short line — the ledger and the tool results carry the record. Continuous execution: Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are the four named below, or all tasks complete. "Should I continue?" prompts and progress summaries waste their time — they asked you to execute the plan, so execute it. Rulings, not stalls. A running plan does not wait on a human. Conflicts, ambiguities, plan defects, a cap you wo

This is an excerpt. Refer to the complete source and its current requirements.