implement-phase

Automate workflow execution by orchestrating a phase implementation plan SI-by-SI, enforcing dependency order, and preventing progression until all required tests for each SI pass successfully.

The best way to execute a phase plan step by step is providing a phase document path or number, which resolves dependencies and pauses between SIs for test verification, with an optional continuous mode available.

SI-by-SI dependency resolution works by resolving the phase document path, executing SIs in strict dependency order, and maintaining a persistent per-SI progress log that reports results and next actions to the user.

Yes, you can run SIs continuously by requesting optional continuous mode, which orchestrates phase execution SI-by-SI while still enforcing dependency order and test validation before advancing.

You need a Tests section in your phase document to trigger per-SI test execution validation; the workflow coordinates testing guidance and only moves to the next SI after current tests pass.

Phase execution stops moving forward because the workflow enforces dependencies and prevents progression to the next SI until all required tests for the current SI pass successfully.