gate-check

A gate check validates project readiness before transitioning between development phases. You need it when moving from stages like Systems Design to Technical Setup or Pre-Production to Production to ensure all artifacts exist and quality criteria are met.

To verify readiness to advance to production, the gate check validates required artifacts across design and architecture domains, coordinates director-panel verdicts, and outputs a clear PASS, CONCERNS, or FAIL result with specific blockers.

Yes, you can automate phase transition validation by applying gate definitions for transitions like Concept to Systems Design or Polish to Release. The system auto-detects current stages and prompts user confirmation before writing progression updates.

Yes, gate check coordinates with a director panel including creative, technical, art, and producer roles to surface READY, CONCERNS, or NOT READY verdicts and guidance for phase transitions.

When a gate check fails or identifies concerns, it outputs a formal verdict detailing specific blockers and missing artifacts required to pass the gate and advance to the next development phase.

Yes, stage progression updates are stored in production/stage.txt. The gate check process writes to this file to maintain an accurate record of the current development phase after a successful transition.