gate-check

To validate project readiness for phase transitions, you can run a phase-gate check that verifies required artifacts like GDDs, ADRs, and playtests, then returns a PASS, CONCERNS, or FAIL verdict with specific blockers and recommendations.

A phase-gate review checks game development repositories for required design and architecture artifacts, test execution results, and playtest data, while also running structural checks like ADR dependency cycles and cross-GDD consistency.

Yes, you can automate release readiness by spawning parallel director subagents for creative, technical, producer, and art assessments, consolidating their READY or NOT READY verdicts into a final phase transition recommendation.

Design reviews handle quality gating by running structural automated checks for artifacts and tests, while explicitly flagging manual checks for areas where automated verification is insufficient to confirm phase readiness.

When a phase-gate review returns a PASS verdict, it can offer governance actions to write the new stage directly to production/stage.txt, but only after receiving explicit user approval to modify the file.

Yes, running a phase transition check requires repository file access to confirm the presence and meaningful content of phase-specific artifacts like GDDs, architecture decision records, and sprint documentation.