review-all-gdds

A cross-CDD consistency review identifies stale references, dependency reciprocity issues, and data ownership conflicts across all module design documents, generating a consolidated review report before architecture planning begins.

Cross-CDD design holism evaluation assesses holistic design alignment across module design documents. It is needed after MVP-tier CDDs are written and before architecture begins to ensure cross-CDD rule consistency.

Cross-CDD review supports both game and general product domains. It applies to all system CDDs located in the design/cdd directory, checking for design conflicts regardless of the specific product domain.

The best way to detect stale references and data ownership conflicts is performing a cross-CDD consistency check, which scans all system CDDs in design/cdd and outputs a consolidated review report detailing design conflicts.

Yes, cross-CDD consistency review explicitly verifies dependency reciprocity across module design documents. It simultaneously checks cross-CDD rule consistency, stale references, and data ownership conflicts to ensure holistic design alignment.

You should avoid cross-CDD consistency review before MVP-tier CDDs are written, as it requires all module design documents to exist in design/cdd to effectively identify cross-CDD inconsistencies and design conflicts.