subagent-driven-development

Subagent-driven development dispatches a fresh subagent for each task in your plan, then runs a code-reviewer subagent after each task completes. This catches issues early and prevents context pollution, enabling fast iteration with built-in quality gates throughout the workflow.

Use fresh subagents for task isolation and inter-task code review checkpoints. This approach solves coordination bottlenecks by ensuring each task executes focused without accumulated context drift, while mandatory reviews catch defects before they compound into later tasks.

Yes. This Skill integrates code-reviewer subagents as mandatory checkpoints between task execution phases—including plan loading, per-task implementation, testing, and review cycles—creating continuous quality assurance without manual handoffs.

Dispatching a fresh subagent for each task isolates execution context and prevents earlier work from biasing later decisions. Combined with inter-task code review, this structure ensures each task starts clean and issues surface immediately rather than accumulating.

Use subagent-driven development when executing plans with largely independent tasks that benefit from isolation, focused reasoning, and staged quality gates. This approach applies to multi-step implementation work where early issue detection and structured iteration prevent compounding defects.

Yes. The Skill includes structured guidance for test-driven development within each task's execution cycle and commit reporting to track progress. The fix-and-iterate workflow ensures testing and review happen at defined checkpoints throughout plan execution.