consistency-check

# Consistency Check Detects cross-document inconsistencies by comparing all GDDs against the entity registry (`design/registry/entities.yaml`). Uses a grep-first approach: reads the registry once, then targets only the GDD sections that mention registered names — no full document reads unless a conflict needs investigation. **This skill is the write-time safety net.** It catches what `/design-system`'s per-section checks may have missed and what `/review-all-gdds`'s holistic review catches too late. **When to run:** - After writing each new GDD (before moving to the next system) - Before `/review-all-gdds` (so that skill starts with a clean baseline) - Before `/create-architecture` (inconsistencies poison downstream ADRs) - On demand: `/consistency-check entity:[name]` to check one entity specifically **Output:** Conflict report + optional registry corrections --- ## Phase 1: Parse Arguments and Load Registry **Modes:** - No argument / `full` — check all registered entries against all GDDs - `since-last-review` — check only GDDs modified since the last review report - `entity:<name>` — check one specific entity across all GDDs - `item:<name>` — check one specific item across all GDDs **Load the registry:** ``` Read path="design/registry/entities.yaml" ``` If the file does not exist or has no entries: > "Entity registry is empty. Run `/design-system` to write GDDs — the registry > is populated automatically after each GDD is completed. Nothing to check yet." Stop an...