review-all-gdds

To check for cross-GDD contradictions, load your summaries and full documents to run bidirectionality, reference, ownership, and formula compatibility checks across all design/gdd/*.md files. This surfaces stale dependencies and systemic design issues before architecture begins.

A cross-system scenario walkthrough validates how game systems interact during key multi-system player moments. It flags undefined behavior, feedback conflicts, and compounded difficulty spikes that only become visible when reviewing all GDDs together.

You need a game economy and progression loop review when multiple MVP GDDs are approved and you must surface competing loops, economic imbalance, or pillar drift. It prevents downstream architecture from being built on conflicting design documentation.

You can scope the GDD review by git changes since the last review by passing an optional focus argument. The review loads full documents and summaries, running consistency and design-theory checks only on modified systems to produce a structured report.

Yes, you can focus the review by issuing the command with an optional focus argument for either consistency or design-theory. Consistency targets reference and formula compatibility, while design-theory surfaces cognitive overload and dominant strategy risks.