consistency-check

Cross-document consistency scanning compares mentions of registered entities, items, formulas, and constants in your GDD markdown files against an authoritative centralized entity registry to detect and report conflicting values.

Run a full consistency audit by loading the centralized entity registry, locating all in-scope GDD markdown files, and executing a grep-first extraction to compare context and flag stale or conflicting attribute values across the documents.

The best way to find stale entity registry entries is to perform targeted consistency checks by entity or item name, which scans GDD mentions and offers registry corrections for entries that have drifted from the authoritative values.

Yes, you can use grep scanning to validate cross-document GDD consistency by performing targeted Grep with limited context to extract nearby attribute and value context, avoiding full document reads unless a conflict requires deep investigation.

Yes, consistency checking works for incremental scans since the last review by locating in-scope GDD markdown files and running targeted grep-first extraction to identify any new conflicting values introduced since the previous audit.

To set up cross-document game design validation, you need an authoritative entity registry formatted as a YAML file and your game design documents stored as markdown files under a designated design directory structure.