subagent-driven-development

Automating code implementation and review involves dispatching independent subagents for each task within a feature plan, followed by a two-stage review process checking spec compliance and code quality. This ensures systematic task execution while maintaining rigorous quality assurance standards.

Subagent-driven development is a workflow that breaks down complex implementation plans into independent tasks, each handled by a dedicated fresh subagent. It enforces TDD adherence and uses defined prompt templates for implementation, spec review, and code quality assessment.

Yes, you can enforce TDD compliance during automated subagent task execution by requiring subagents to follow Test-Driven Development principles and adhere to defined prompt templates for implementation, ensuring code quality and spec compliance throughout the workflow.

Subagent-driven development works for multi-task feature plans within a single session by dispatching a fresh subagent for each distinct task. It applies to complex development workflows requiring systematic execution and rigorous quality assurance across all decomposed tasks.

The best way to ensure spec compliance in automated development workflows is implementing a two-stage review process with separate checks for spec compliance and code quality after each task. This verifies that subagents adhere to defined specifications and maintain high code standards.

You should avoid using a subagent-driven workflow for feature implementation when your plan lacks multiple distinct sub-tasks or when your development workflow does not require systematic task execution and rigorous two-stage quality assurance reviews for spec compliance and code quality.