design-review

To review a game design document for completeness, run a structural checklist covering the overview, fantasy, rules, formulas, edge cases, and dependencies. This validates the GDD against design standards and outputs a structured verdict with blocking revisions.

Dependency validation in GDD pre-production QA uses local file discovery to confirm that each declared dependency's design document exists on disk. It checks file paths via globs and reports missing references to prevent broken cross-system links during implementation.

Yes, you can run a consistency check on game design formulas and edge cases. The audit verifies that mathematical formulas align with described behavior and flags underspecified hand-wave sections that would force programmers to guess during implementation.

You audit systems design dependencies by running a review skill on your design document path. It validates dependency GDD file existence via local globs, ensuring cross-system references resolve correctly before production starts.

Lean mode performs a direct review of the game design document, while full mode spawns specialist Tasks for adversarial review across game design and systems domains. Full mode synthesizes a senior verdict, whereas lean provides faster standard compliance verification.

Game design documents need implementability verification to catch missing sections, unclear rules, and broken dependencies before coding starts. This pre-implementation audit reduces rework and design drift by forcing designers to specify tuning knobs and acceptance criteria.