subagent-driven-development

Topics in the source

• Subagent-Driven Development
• Overview
• When to Use
• Roles
• The Process
• 1. Read and Parse Plan
• 2. Per-Task Workflow
• Step 1: Dispatch Implementer Subagent

Execute implementation plans by dispatching a fresh subagent per task with systematic two-stage review. Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration. Method adapted from the public superpowers subagent-driven-development flow (MIT); the role names and the transport-neutral dispatch contract are this port's. Use this skill when: You have an implementation plan (from writing-plans or equivalent user requirements) Tasks are mostly independent Quality and spec compliance are important You want automated review between tasks vs. manual execution: Fresh context per task (no confusion from accumulated state) Automated review process catches issues early Consistent quality checks across all tasks Children may lack the parent's interactive tools: state every constraint up front rather than expecting a child to ask Names in the source material were agent products; they are roles here. | Role | Owns | |---|---| | controller | reads the plan once, dispatches, tracks status, enforces review order, integrates | | implementer | one task, full task text, the project's conventions, a report of files/tests/verification | | spec reviewe

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