gate-check

Phase gate readiness validation checks required artifacts and quality criteria for the target gate, producing a structured PASS, CONCERNS, or FAIL verdict to confirm release readiness before advancing phases.

A phase gate readiness check prevents teams from advancing to the next development phase before the right artifacts and quality gates are in place, reducing late-stage rework and missed blockers across project phases.

Run a readiness check for a specific transition, like Technical Setup to Pre-Production, by executing the gate-check command with the target stage name to validate required files and architecture alignment.

Yes, phase gate validation optionally runs parallel director assessments across creative, technical, producer, and art domains in lean or full review modes to catch readiness gaps beyond simple file presence.

Yes, the phase gate validation supports auto-detection of the current development stage with user confirmation, reading repository files and directories to validate artifact content before producing a readiness verdict.

When artifact validation produces a PASS verdict and is confirmed by the user, the phase gate check automatically updates the production stage status file with the new stage name to reflect the phase advancement.