review-all-gdds

To review GDD consistency before architecture, scan your repository's design/gdd directory to detect cross-document contradictions, stale references, and formula mismatches. This validates design coherence across all system documents before structural implementation begins.

Validating game design coherence across system GDDs involves mapping economic loops, assessing progression competition, and detecting dominant strategies. It checks pillar alignment and player-fantasy coherence to surface emergent design hazards before architecture.

You should perform a cross-GDD consistency check after drafting MVP GDDs or completing a major revision. Running this review before creating architecture prevents inconsistent design rules and formula mismatches from being baked into structural systems.

Yes, you can automatically update your systems index after reviewing game design documents. The review process produces a consolidated dated report and offers controlled file updates with user consent to maintain registry accuracy.

The best way to detect formula range compatibility issues in game design files is to perform full-document reads across multiple GDD Markdown files. This compares tuning-knob ownership and analyzes formula ranges to identify mismatches.

Yes, cross-GDD review works with Markdown files stored in a single repository. It applies to repositories containing design/gdd files, utilizing multi-pass loading and optional registry pre-load to limit token usage during full-document reads.