Blueprint: inspect

Read ${CLAUDE_PLUGIN_ROOT}/FORMAT.md first (or FORMAT.md at the repo root if you are working inside the blueprint repo itself).

Read-only. This skill reports; it does not edit. Offer fixes, apply none without being asked.

Gather

Run these against .blueprint/<slug>/ and work from the output — do not eyeball the documents:

rg -o '^### (R\d+)'            requirements.md   # declared requirements
rg -o '\*\*(R\d+\.AC\d+)\*\*'  requirements.md   # declared criteria
rg -o '^### (C\d+)'            architecture.md   # declared components
rg -o 'covers: *(.+)$'         architecture.md   # coverage claims
rg -o '\*\*(T\d+)\*\*'         tasks.md          # declared tasks
rg -o '→ *(C\d+|chore) *\| *(.+)$' tasks.md      # task citations
rg -o '\*\*(Q\d+)\*\*'         requirements.md architecture.md
rg -n 'status: answered'       requirements.md architecture.md
rg -n 'status: dropped'        requirements.md architecture.md tasks.md

Checks

If a document is missing, report which step has not run yet and stop — do not report 40 failures because architecture.md does not exist.

Read declarations, not token occurrences. These documents describe Blueprint's own grammar, so files:, status: dropped and covers: all turn up inside ordinary prose. A marker counts only where the format puts it: at the start of its line, in the document that owns it. A phantom id lifted out of a sentence is worse than a missed one, because it sends the reader hunting for something that was never declared.

Output

A short table, then the specifics. Nothing else.

Blueprint: token-refresh

  requirements   7 R, 19 AC
  architecture   5 C
  tasks          12 T, 3 phases

  FAIL  R4 covered by no component
  FAIL  T9 cites C6, which does not exist
  FAIL  R2.AC3 cited by no task
  WARN  Q2 unanswered
  WARN  T5 has no files: line

  3 failures, 2 warnings.

When everything passes, say so in one line with the counts. Do not pad.

For each failure, name the cheapest fix in a few words ("R4: add a component or drop the requirement"). Then ask whether to apply them. Do not start editing.