review-all-gdds

To check multiple game design documents (GDDs) for cross-system inconsistencies, run a holistic review process that scans finalized MVP system GDDs to detect dependency asymmetries, rule contradictions, stale references, and ownership conflicts across all loaded files.

Cross-document validation in game development is the process of reviewing all system GDDs together to identify holistic design flaws and dependency asymmetries that individual per-GDD reviews miss, ensuring design theory compliance before architecture development begins.

You should run a holistic game design review after all MVP system GDDs are finalized and before starting architecture prep. This timing validates cross-document consistency and prevents costly rework caused by building architecture on flawed or contradictory design documents.

You detect dominant strategies and economic imbalances across game systems by applying a game design holism review that evaluates all systems together, exposing progression loop conflicts, formula incompatibilities, and cognitive overload risks that individual documents do not surface.

Pillar drift and cross-system interaction failures in game design are caused by conflicting progression loops and incompatible player fantasies emerging when systems are viewed together. A cross-GDD review identifies these holistic flaws before architecture development.

No, individual per-GDD reviews cannot find formula incompatibilities and stale references across multiple systems. You need a cross-document validation process that scans all finalized MVP system GDDs together to surface these specific cross-system design flaws.