implement-phase

Phase orchestration uses an eight-step pipeline with automatic progression, spawning subagents for implementation, verification, code review, ADR compliance, and plan synchronization. It enforces fix loops to achieve a clean PASS across all steps and produces a final completion report.

You need subagents for code review and ADR compliance to enforce a strict orchestration model. By delegating these specialized tasks, the pipeline maintains automatic progression, runs built-in fix loops, and produces auditable logs for the final completion report.

Yes, phase implementation with code changes and plan synchronization runs without manual intervention. The orchestration model enforces automatic progression through an eight-step pipeline, using subagents to handle implementation, verification, and archival while collecting results for a completion report.

Executing an implementation phase with ADR compliance and verification is best handled by an orchestration pipeline. It spawns subagents for each task, applies automatic progression through an eight-step pipeline, and enforces fix loops to achieve a clean PASS across all quality gates.

You need automated quality gates when a plan specifies a phase requiring code changes, verification, and plan synchronization as a cohesive pipeline. The orchestration model enforces these gates using subagents, automatic progression, and fix loops to achieve a clean PASS and generate a completion report.

The orchestration model is limited to phases where code changes, verification, ADR compliance, and plan synchronization must be performed as a cohesive pipeline. It requires spawning multiple subagents and relies on an eight-step pipeline with automatic progression and fix loops to achieve a clean PASS.