gate-check

Game production phase readiness is validated by checking required design, architecture, engineering, and QA artifacts against specific transition gates. The system outputs a PASS, CONCERNS, or FAIL verdict with explicit blockers and next actions.

A phase gate review enforces artifact validation by verifying required files exist with meaningful content and validating review verdicts. It flags manual verification items without assuming success to ensure quality gates are met.

To check if your project is ready to move to production staging, run a readiness check for the target transition. The system auto-detects the current stage or accepts a specified phase to evaluate required artifacts.

Yes, collaborative director reviews can strengthen a phase gate verdict. In lean or full modes, the system aggregates assessments from Creative, Technical, Producer, and Art directors using parallel gate protocols.

When a phase gate readiness check returns a PASS verdict, it guides updating the production/stage.txt file to advance the studio pipeline state to the next development phase.

Automated phase gate checks rely on file system verification and cannot bypass missing artifacts. If required files lack meaningful content or manual verification items are incomplete, the check outputs a FAIL or CONCERNS verdict with explicit blockers.