gate-check

Game development phase readiness is validated by checking for required artifacts like GDDs, ADRs, and tests, producing a structured PASS, CONCERNS, or FAIL verdict to prevent false starts and rework.

A phase gate check in game development quality assurance enforces required artifact presence and quality criteria across transitions like Concept to Systems Design to Technical Setup, performing cross-document consistency checks before advancing.

GDD and ADR consistency is ensured by performing cross-document consistency checks during artifact verification, validating that design and technical decisions align before producing a phase advancement verdict.

Workflow selection gates run a human-driven decision interview to recommend either Hybrid or Full OCGS workflows, updating production workflow and stage files only after explicit user confirmation.

Release readiness validation requires artifacts appropriate to the target phase, including expected GDDs, ADRs, architecture readiness, sprints, vertical slice evidence, tests, and release checklists.

Automated phase gate validation should not be used when required repository artifacts are missing, as it enforces artifact presence and quality criteria, returning a FAIL verdict with explicit blockers instead of proceeding.