review-all-gdds

To check multiple game design documents for cross-document inconsistencies, run a cross-CDD review that simultaneously reads all in-scope CDDs to compare module indexes, dependencies, rules, tuning knobs, and acceptance criteria. This process detects contradictions, stale references, and design drift across the system set before outputting a revision report.

Design holism analysis in multi-module product reviews is a technique that evaluates the entire system for competing value loops, cognitive overload, dominant paths, and principle alignment issues. These are structural conflicts that single-document reviews miss when assessing interconnected product or game systems.

You can trace multi-module user flows by conducting scenario walkthroughs across all in-scope CDDs. This method traces user paths through multiple modules to uncover broken state transitions, contradictory messaging, double-processing, and undefined behavior that only surface during cross-document analysis.

You need to run a cross-CDD consistency check after multiple CDDs are drafted or revised, but before architecture work begins. This ensures the full product or game system stays coherent and catches ownership conflicts and stale references early in the design phase.

Yes, you can use scenario walkthroughs alongside cross-document consistency checks to detect tuning conflicts across game modules. By comparing tuning knobs and tracing multi-module user flows, the review identifies contradictory parameters and double-processing issues across the system set.