review-all-gdds

To find contradictions across game design documents, you can perform a holistic GDD review that cross-references all system documents to identify stale cross-references, ownership conflicts, and incompatible formulas. This ensures alignment before architecture begins.

Checking game design holism involves reviewing all system GDDs together to flag player-facing systemic issues like competing progression loops, dominant strategies, economic imbalances, and pillar drift that isolated document reviews miss.

You need a cross-document consistency review during post-MVP GDD phases when multiple subsystems must align. It synchronizes game concept context and validates interaction boundaries before architecture starts to prevent silent design propagation.

Validating interaction boundaries requires walking through key multi-system player scenarios to surface ordering and state-transition failures. This scenario walkthrough report outputs blocking or warning severities for unaligned subsystems.

Yes, you can use optional focus modes like consistency-only, design-theory-only, or since-last-review scope. These modes run parallel passes on the synchronized GDD set to target specific cross-document checks without a full review.

Incompatible formulas and tuning knob ownership conflicts arise when isolated subsystem GDDs are approved separately. A holistic review detects these stale references and input-range incompatibilities by applying an optional entity registry baseline.