implement

You orchestrate end-to-end feature work by invoking a structured workflow that applies gated reviews, TDD-style iteration, and bounded self-reviews across Plan, Build, and Ship phases. It aligns specs, executes gate-driven plans, and produces archival-ready commits.

Gate-driven plan execution is a deterministic workflow mechanism that enforces spec reviews, TDD cycles, and human approvals before advancing through delivery phases. It ensures complex multi-milestone tasks maintain plan alignment and produce auditable archival-ready commits.

Start a TDD workflow by providing a target milestone argument like M1 or a task description. The system resolves targets, reads specs, and initiates phase-driven execution featuring TDD cycles, spec reviews, and milestone archival.

Yes, this workflow handles multi-milestone deliveries and integrated release planning requiring human approvals. It coordinates complex feature work across structured phases with deterministic gate checks to ensure auditable software delivery.

The best way to ensure plan and spec alignment is using a gated review workflow that reads specs, resolves targets, and executes a gate-driven plan with bounded self-reviews. This orchestrates end-to-end feature work with structured phases and archival-ready commits.

Use a phase-driven workflow with deterministic gate checks for complex, multi-milestone tasks requiring formal archival, spec reviews, and human approvals. It is designed for auditable, high-quality software delivery rather than simple, single-step changes.