review-all-gdds

To check for contradictions across game design documents, you can run a cross-document review that detects dependency asymmetries, rule conflicts, stale references, and formula mismatches across all system GDDs before architecture begins.

Incremental GDD review using git history works by parsing only the game design documents changed since the last review report, ensuring faster consistency checks by skipping unchanged markdown files.

You need a cross-document consistency check for game design when your project has multiple system GDDs and you are entering the pre-architecture phase, requiring holistic validation to surface hidden design theory violations.

You can detect design theory violations like dominant strategies, economic imbalances, competing progression loops, and pillar drift by applying a concurrent design-theory analysis across all your game design documents.

You need the ability to parse markdown files in your design/gdd directory to run a game design document review. Git history is optional and only required if you want to utilize the incremental review mode for changed files.