subagent-driven-development

Executing an implementation plan with independent subagents involves dispatching a fresh subagent per task to ensure context isolation, followed by a mandatory two-stage review for spec compliance and code quality. This process ensures independent task execution and rigorous quality control.

The two-stage review process for subagent-driven development requires each task to undergo a spec compliance review followed by a code quality review. This mandatory process ensures that every subagent's execution meets the implementation plan specifications and maintains high code production standards.

Managing feature development tasks independently requires decomposing the implementation plan into distinct tasks such as creating a database schema or building an API endpoint. A dedicated subagent executes each task with a clean context to prevent pollution from previous tasks, followed by a two-stage review.

Yes, you need subagents to be available to use subagent-driven development, as the skill dispatches a fresh subagent for each independent task. Additionally, the implementation plan must contain independent tasks to ensure proper context isolation and execution.

Context isolation matters when dispatching subagents for code production because it ensures each subagent operates with a clean context, preventing pollution from previous tasks. This approach maintains the independence of each task execution and supports rigorous quality control during the two-stage review.

You should not use subagent-driven development when subagents are unavailable or when the implementation plan lacks independent tasks. The execution engine requires both available subagents and a plan decomposed into independent tasks to properly perform task execution and the mandatory two-stage review.