consistency-check

Run a consistency check to compare registered entities, items, formulas, and constants across all design/gdd/*.md files. This grep-first scan targets only sections mentioning registered names to detect divergent stats, conflicting item values, or incompatible formula variables.

A grep-first workflow validates GDD consistency by loading the entity registry at design/registry/entities.yaml first, then scanning design docs for matches. It collects context around matches to report conflicts and flags stale registry entries for review without reading full documents.

The best way to detect conflicting entity stats is to cross-reference your design docs against an authoritative registry. Comparing registered entities, items, and constants across all GDD sources surfaces mismatches and generates a report referencing the authoritative registry source.

Yes, you need an entity registry at design/registry/entities.yaml to scan GDDs for mismatches. The registry provides the authoritative source values required to detect divergent stats, conflicting item values, and incompatible formula variables across your design/gdd/*.md files.

Run a consistency check on your design docs when a new GDD is added or an existing one is updated. This surfaces cross-document inconsistencies before architecture decisions, flagging stale registry entries and guiding the resolution process to align GDDs with the registry.