design-review

A game design document (GDD) review identifies design gaps, validates dependencies, and surfaces actionable blockers before programmer handoff. It checks phase-driven completeness and cross-reference alignment to ensure clear implementation steps.

Checking internal consistency in a GDD requires validating cross-references and dependencies against project design standards. A design review surfaces inconsistencies and provides concrete, testable findings to align the specification with project requirements.

Yes, the full design review mode includes adversarial specialist assessments for game design. This surfaces hidden gaps and implementation risks, providing concrete remediation steps and handoff guidance to ensure the GDD is ready for programmers.

Yes, you can use this design review to validate cross-reference alignment with project standards. It analyzes the GDD to ensure dependencies adhere to project design standards, outputting actionable blockers and recommended next steps for implementation.

Automated GDD QA focuses on structural completeness, consistency, and implementability rather than creative design choices. It surfaces testable findings and dependency risks but does not evaluate subjective gameplay fun, serving strictly as a pre-implementation gap checker.