implement-phase

Phase execution stops advancing when tests fail after an SI implementation. The workflow runs a fix loop for up to three iterations to resolve test failures, enforcing a hard stop if issues persist until the user intervenes.

Yes, test-driven progress applies to multi-SI projects across subprojects by validating each SI with tests before advancing. Progress is tracked via a phase progress artifact, ensuring auditable completion and dependency-aware sequencing throughout the workflow.

The required workflow to implement phase plans involves planning the SI, implementing actions, writing tests, running tests, and fixing up to three iterations. It enforces a hard stop between SIs, pausing for user confirmation before proceeding to the next SI.

A hard stop between SIs is needed during phase execution to enforce controlled progression and verify tests pass. It prevents moving to the next SI until the current implementation is validated and the user explicitly confirms continuation.