Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run after all MVP GDDs are written, before architecture begins.
This skill reads every system GDD simultaneously and performs two complementary reviews that cannot be done per-GDD in isolation:
This is distinct from /design-review, which reviews one GDD for internal
completeness. This skill reviews the relationships between all GDDs.
When to run:
/create-architecture begins (architecture built on inconsistent GDDs
inherits those inconsistencies)Argument modes:
Focus: $ARGUMENTS[0] (blank = full)
full: Both consistency and design theory passesconsistency: Cross-GDD consistency checks only (faster)design-theory: Game design holism checks onlysince-last-review: Only GDDs modified since the last review report (git-based)Before reading any full document, use Grep to extract ## Summary sections
from all GDD files:
Grep pattern="## Summary" glob="design/gdd/*.md" output_mode="content" -A 5
Display a manifest to the user:
Found [N] GDDs. Summaries:
• combat.md — [summary text]
• inventory.md — [summary text]
...
For since-last-review mode: run git log --name-only to identify GDDs
modified since the last review report file was written. Show the user which
GDDs are in scope based on summaries before doing any full reads. Only
proceed to L1 for those GDDs plus any GDDs listed in their "Key deps".
Before full-reading any GDD, check for the entity registry:
Read path="design/registry/entities.yaml"
If the registry exists and has entries, use it as a pre-built conflict baseline: known entities, items, formulas, and constants with their authoritative values and source GDDs. In Phase 2, grep GDDs for registered names first — this is faster than reading all GDDs in full before knowing what to look for.
If the registry is empty or absent: proceed without it. Note in the report:
"Entity registry is empty — consistency checks rely on full GDD reads only.
Run /consistency-check after this review to populate the registry."
Full-read the in-scope documents:
design/gdd/game-concept.md — game vision, core loop, MVP definitiondesign/gdd/game-pillars.md if it exists — design pillars and anti-pillarsdesign/gdd/systems-index.md — authoritative system list, layers, dependencies, statusdesign/gdd/ — read completely (skip
game-concept.md and systems-index.md — those are read above)Report: "Loaded [N] system GDDs covering [M] systems. Pillars: [list]. Anti-pillars: [list]."
If fewer than 2 system GDDs exist, stop:
"Cross-GDD review requires at least 2 system GDDs. Write more GDDs first, then re-run
/review-all-gdds."
Phase 2 (Consistency) and Phase 3 (Design Theory) are independent — they read the same GDD inputs but produce separate reports. Spawn both as parallel Task agents simultaneously rather than waiting for Phase 2 to complete before starting Phase 3. Collect both results before writing the combined report.
Work through every pair and group of GDDs to find contradictions and gaps.
For every GDD's Dependencies section, check that every listed dependency is