design-review

Validating a game design document requires checking for missing sections, internal contradictions, and broken dependencies. The design-review process verifies completeness checklists, formulas, and cross-system interactions to produce actionable, testable specs before development begins.

A consistency review requires your game design document to include Overview, Player Fantasy, Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria sections. It checks for internal contradictions, implementation gaps, and performance implications across cross-system interactions.

Checking game design dependencies involves validating declared dependencies against files in the design/gdd/ directory. The review reads CLAUDE.md and prior review logs to surface project-aware dependency conflicts and disagreements for user adjudication.

Running an adversarial specialist review is possible in full depth mode. It spawns parallel specialist subagents such as game-designer, systems-designer, and qa-lead, then synthesizes their findings via a senior creative-director to deliver a comprehensive consistency report.

The design review process applies to GDD files located in the design/gdd/ directory and related project docs. It relies on repository file reads and Glob/Grep checks to validate dependencies and ensure lore alignment across the project.

Automated game design document reviews depend on repository file reads and interactive AskUserQuestion widgets to present next-step options. They cannot resolve dependency disagreements autonomously; instead, they surface conflicts for user adjudication and require existing project documentation to function.