review-all-gdds

To check for cross-GDD inconsistencies, you need a structured review process that loads multiple system GDDs to detect dependency asymmetry, contradictions, and stale references. This surfaces design conflicts before development proceeds.

Pillar drift occurs when multiple game systems deviate from core design pillars. A holism analysis pass across all GDDs reveals this drift, alongside dominant strategies and economic imbalances, ensuring overall game design consistency.

You should run a cross-document consistency check after your MVP GDDs are written. Triggering the review at this stage generates a formal Cross-GDD Review Report with actionables, resolving stale references and ownership conflicts before architecture is finalized.

Yes, you can track review progress by updating the status in your systems index and production session state. This optional step follows the phase-based workflow, ensuring cross-GDD review outcomes are logged directly into your production tracking.

The best way to resolve stale references is a multi-phase review workflow that loads relevant GDDs and runs consistent checks. This identifies dependency asymmetry and outputs a formal report with actionable steps to correct the references.

A cross-GDD review applies to projects with multiple system GDDs. If you only have one core design document, cross-document dependency asymmetry and contradictions will not be present, making this multi-phase holism analysis unnecessary.