consistency-check

Cross-document validation for game design documents involves loading a centralized entity registry and comparing registered entities, items, formulas, and constants against GDD sections. The process uses targeted grep-based scanning to identify mismatched stats or values before architecture work begins.

Consistency checking for game design documents is needed during GDD authoring, review, and pre-architecture workflows. Run it after authoring a new system GDD to find mismatched entity stats, item values, or gameplay constants before inconsistencies spread into implementation.

You can validate specific entities or items by running the consistency check with entity:name or item:name parameters. This targets only document sections mentioning those registered entries, reducing unnecessary full-document reads during the validation process.

Conflict resolution investigates discrepancies, distinguishes genuine conflicts from stale registry data, records failures, and supports optional registry corrections. The workflow also includes session-state logging to track validation outcomes across multiple review cycles.

A centralized entity registry containing entities, items, formulas, and constants must be loaded before checking design document consistency. This registry serves as the reference baseline for comparing against relevant GDD sections during validation.

The best way to catch design inconsistencies before architecture work is to run registry-based cross-document validation after authoring a new system GDD. This grep-first approach targets only sections mentioning registered entries, finding mismatched entity values early without full-document reads.