review-all-gdds

Cross-system contradictions in game design documents are checked by reviewing all GDD markdown files together to detect dependency asymmetry, stale references, rule conflicts, and ownership disputes across multiple systems.

Holistic design issue reviews should be executed after MVP-tier system GDDs are individually approved and before systems architecture begins, ensuring dependencies, progression loops, and player fantasy are consistent.

Economic balance and progression loop conflicts are found by running pairwise rule, economy, and design-theory checks across all relevant GDDs to flag competing loops, dominant strategies, and difficulty curve mismatches.

A cross-system scenario walkthrough walks key multi-system gameplay moments to identify interaction-boundary failures like race conditions, undefined state transitions, reward conflicts, and compounding difficulty spikes.

Yes, bidirectional dependencies and references can be validated optionally using an entity registry baseline while scanning all relevant GDD markdown files to ensure structural consistency across systems.

A full GDD consistency check is intended strictly for post-MVP phases and requires reading all relevant markdown files, meaning it cannot validate incomplete systems or substitute for individual GDD approval processes.