phase-enforcement

To enforce evidence-based completion of development phases, you need a mechanism that validates required artifacts and prevents premature closure. This skill checks for required files, maps validation criteria, and blocks phase progression until evidence is verified.

Preventing premature code review completion requires artifact verification. The system checks if the consolidated review file exists and contains a PASS verdict, blocking any phase updates that lack the required evidence-based documentation.

Managing outer loop retry logic involves tracking iteration limits and verifying previous phase success. This orchestration mechanism enforces these constraints mechanically, ensuring phases cannot proceed until prior workflow stages are successfully validated.

Validation mapping ensures requirements are met by comparing Phase 1 criteria directly against Phase 7 results. This cross-phase validation provides auditable proof that initial requirements were satisfied before allowing the development phase to close.

Enforcing development process quality gates requires integration with task updates and session state tracking. This setup provides the mechanical enforcement needed to validate artifacts and manage outer loop iterations without relying on manual checks.

If required artifacts are missing, phase completion is blocked. The enforcement mechanism validates the existence of necessary files and show-your-work evidence, preventing any premature phase closure until all validation criteria are satisfied.