gate-check

To validate phase transition readiness, you run a gate-check against the target development phase to verify required artifacts and apply quality checks. It generates a formal PASS, CONCERNS, or FAIL verdict with actionable blockers.

A phase-gate validation check enforces governance by verifying required artifacts and quality standards before a project advances between stages. It ensures teams successfully complete all required documents from Concept through Release.

You enforce artifact presence and quality checks by applying a gate-check to the target phase, such as Pre-Production or Production. It surfaces missing documents and blockers to guide the team through transition governance.

Yes, when phase advancement is approved, the gate-check can automatically update the stage state file at production/stage.txt. This records the formal PASS verdict and advances the project to the next development phase.

Gate-driven progression checks support phase validation across Concept, Systems Design, Technical Setup, Pre-Production, Production, Polish, and Release. Each stage requires specific artifacts to pass quality gates before transitioning.

A CONCERNS verdict indicates the phase transition is not fully blocked but has unresolved quality check issues or missing artifacts. It differs from a FAIL by allowing conditional advancement while surfacing actionable blockers.