check-docs-consistencylisted

# Check Docs Consistency Stateless scan. Read docs, cross-reference, write timestamped report. Report-only — resolution is the user's call. ## When to Use User invokes `/check-docs-consistency` when: - Starting a new feature pipeline (verify source of truth before writing specs) - Drift pain surfaces ("wait, didn't we decide the opposite?") - After a batch of merges that touched multiple docs - Periodically as a health check (weekly or per-milestone) ## Doc Surface The scan reads `**/*.md` at any depth and keeps the authored project docs. The filter drops generated and vendored Markdown — paths under `node_modules/`, `vendor/`, `.git/`, `dist/`, `build/`, `target/`, `.venv/`, and the scan's own `.review/` reports. The kept set is the doc surface, wherever the project holds it: a `docs/` tree, a root `README` plus scattered `*.md`, `documentation/`, `.github/`, or any mix. The glob already includes the orchestration files (`CLAUDE.md`, `.claude/agents/*.md`, `.claude/skills/**/SKILL.md`); Step 1 mines those specifically for path references and ownership statements. Extend the exclusion list per project when a tree carries `*.md` that is generated or vendored output rather than authored project doc (e.g. `.next/`, `coverage/`, `__pycache__/`). ## Procedure ### Step 0: Pre-flight — Block If a Prior Report Is Unprocessed Glob `.review/docs-consistency-*.md`. (Step 0 reads `.review/` to find prior reports; Step 1's doc-surface scan excludes that same dir — see Doc Surfa