gate-check

Phase validation works by checking universal criteria like code, gameplay, assets, and Git hygiene, alongside per-phase specifics. It emits a definitive PASS, CONCERNS, or FAIL verdict with concrete blockers to confirm whether a phase is truly completed.

Automating phase closure checks involves running deterministic validations against code, gameplay, assets, and Git hygiene. This generates a clear verdict with actionable blockers, ensuring nothing is missed before moving to the next development phase.

You validate per-phase criteria by applying deterministic checks to phase-specific requirements alongside universal standards. Providing the phase number when prompted yields a decisive verdict detailing any remaining blockers for that specific phase.

Yes, phase validation updates CLAUDE.md and project primers based on the emitted verdict. This ensures project documentation accurately reflects the current phase status and any identified blockers or concerns.

When validation returns a CONCERNS or FAIL verdict, it outputs concrete blockers detailing what failed. You must resolve these specific blockers in code, gameplay, assets, or Git before the phase can be declared complete.