review-all-gdds

To detect cross-GDD conflicts before architecture, review all approved game design documents holistically to identify contradictions, stale references, ownership conflicts, and incompatible formulas across systems.

You need a holistic game design audit after all MVP game design documents are individually approved to detect competing progression loops, economic imbalances, difficulty-curve mismatches, and pillar drift before production handoff.

Trace multi-system player moments during a design review to expose race conditions, feedback loops, broken state transitions, reward conflicts, and undefined behavior across interconnected game systems.

Yes, you can specify a design-theory focus to analyze competing progression loops, economic imbalances, and conflicting player fantasies without validating every individual system dependency.

Cross-GDD consistency analysis requires access to the project's game design documents, design pillars, systems index, entity registry, and engine preferences to accurately detect systemic design risks.

The best way to validate game economy and progression dependencies is a full consistency review that compares tuning knobs and formulas across all game design documents to flag economic imbalances and dominant strategies.