What problem does it solve? Coordinating multi-phase implementation work across independent sub-phases is slow and error-prone when done sequentially in a single context, and teams lack a structured way to parallelize work while preserving review quality and TDD discipline. ## Core Features & Use Cases - Parallel Subagent Dispatch: Spawns implementer subagents per independent sub-phase (SP1, SP2, SP3) and aggregates results with two-stage spec and code-quality review. - Automatic Sequential Fallback: Detects subagent capability at runtime and falls back to sequential execution with extended self-review when subagents are unavailable. - Phase 3.5 Code Review Loop: Dispatches a dedicated code-reviewer subagent with severity classification (Critical/Important/Minor) and re-review cycles until approval. - Use Case: A feature touching API, UI, and database layers is split into three independent sub-phases, each implemented by a separate subagent in parallel, reviewed, then validated with parallel unit, integration, and E2E test subagents. ## Quick Start Ask the agent to parallelize Phase 3 implementation by dispatching an implementer subagent for each independent sub-phase in the locked TO-BE plan.