gate-check

Production readiness validation checks required artifacts, quality standards, and blockers before advancing development phases. It produces a PASS, CONCERNS, or FAIL verdict with blockers and recommendations to confirm stage transitions.

Phase gates are readiness checkpoints between development stages like Systems Design to Technical Setup. They require specific artifacts and quality expectations to be met, preventing teams from advancing without confirming required deliverables.

Automated quality checks validate file presence, content, and test status while prompting for manual checks like playtesting or design reviews. This surfaces blockers and confirms artifact verification before proceeding to the next phase.

Yes, gate-check supports manual quality prompts and blocker reporting. It flags manual checks such as design reviews alongside automated validation, generating a comprehensive report with blockers and recommendations.

Phase-gate validation asks for approval to update production/stage.txt after generating a PASS, CONCERNS, or FAIL report. This captures a release-ready sign-off and updates the stage status before advancing.

Artifact validation is needed when transitioning between development phases like Concept through Release. It confirms required artifacts, quality standards, and stage-specific criteria exist, blocking hidden risks and misalignment before moving forward.