phase-enforcement

What problem does it solve?

This Skill prevents developers from prematurely marking development phases as complete without providing necessary evidence, documentation, or passing validation checks, ensuring a robust and auditable development process.

Core Features & Use Cases

• Artifact Verification: Ensures required files (e.g., requirements.md, architecture.md, validation/result.md) exist before a phase can be marked complete.
• Validation Mapping: Compares Phase 1 criteria against Phase 7 results to ensure requirements are met.
• Outer Loop Control: Manages iteration limits and ensures successful completion of previous phases before proceeding.
• Show-Your-Work Enforcement: Mandates clear, evidence-based reporting of results, not just a confirmation of completion.
• Use Case: When a developer claims "Phase 5: Code Review Complete," this skill will automatically check if the reviews/code-review/consolidated.md file exists and contains a "PASS" verdict, blocking completion if it's missing.

Quick Start

Before marking any phase complete, run the checkpoint verification script for the current phase.