subagent-driven-development

Plan execution orchestration dispatches a fresh subagent per task, ensuring isolated context and preventing cross-task contamination. This approach reduces context switches and enables rapid iteration with built-in review loops.

Two-stage review is a quality control process that evaluates task completion in sequence: first verifying spec compliance, then assessing code quality. This structured loop ensures each dispatched subagent meets both functional and quality standards.

Context isolation is needed when coordinating complex plans with multiple, largely independent tasks. It prevents cross-task contamination by assigning each task to a fresh subagent, improving execution speed and quality.

Task dispatch handles lifecycle events through specific signals: DONE, BLOCKED, NEEDS_CONTEXT, and DONE_WITH_CONCERNS. These escalation signals manage task queue progression and flag tasks requiring intervention.

The best way to manage a task queue with independent subagents is using workflow orchestration that creates per-task subagents, applies two-stage reviews, and processes lifecycle signals to track progression and handle escalations.

Subagent-driven development applies to sessions with multiple, largely independent tasks. It is not suited for tightly interdependent steps, as context isolation prevents subagents from sharing state across tasks.