subagent-driven-development

To isolate context for independent tasks, you can dispatch a fresh subagent per task within your current planning session. This approach maintains clean context per task, preventing cross-task context pollution and enabling rapid iteration.

Automating spec compliance and code quality reviews is best handled through a two-stage review process per task. This requires a spec-compliance review to prevent scope creep, followed strictly by a code-quality review before marking the task complete.

You can automatically track task completion by dispatching subagents per plan task and enforcing two-stage reviews. The system marks tasks complete after successful reviews and seamlessly moves to the next task in the workflow.

Subagent task dispatch is applicable for largely independent tasks in a single planning session. It enforces per-task isolation, so it is not suited for tasks with heavy dependencies that require shared context across steps.

Complex plan execution bottlenecks in a single context due to accumulated context pollution. Dividing work among fresh subagents per task eliminates this bottleneck by ensuring clean context and rapid iteration for each step.