design-review

Game design document review involves checking the document for missing sections, broken dependency references, internal inconsistencies, and implementation blockers before development proceeds. It validates formulas, edge cases, and system dependency lists for single- or multi-system features.

Dependency validation in a game design document checks that referenced system GDD files actually exist on disk. It ensures the dependency graph is intact and that all cross-system feature references are valid before programming begins.

You can check your GDD for missing sections and implementation blockers by running a depth-controlled review using the command /design-review path-to-design-doc --depth full, which validates formulas, edge cases, acceptance criteria, and system dependencies.

Yes, you can adjust GDD review depth using the --depth argument with full, lean, or solo options. Full mode delegates to adversarial specialists across multiple domains like economy and combat, while lean and solo modes prioritize faster turnaround.

Yes, design review works for both single- and multi-system game features. It applies to GDDs that contain formulas, edge cases, acceptance criteria, and system dependency lists across complex feature scopes.

A full game design document review outputs a structured verdict, a scope signal, and specialist-sourced issues. It distinguishes between blocking and recommended revisions, highlights specialist disagreements, and identifies implementation blockers.