Verify the bootstrap by checking that CLAUDE.md, spec.org, and memory files correctly answer the five verification questions. Use after full bootstrap.
This skill is inherently idempotent -- it reads files and reports findings. Running it multiple times is expected and safe.
Before verifying, confirm the minimum scaffold exists:
CLAUDE.md must exist. If not: stop with "run /generate-claude-md first."spec.org must exist. If not: stop with "no spec.org found."If both exist, proceed with verification.
Read CLAUDE.md, spec.org, and memory files, then answer:
What is this project? Expected: MCP server exposing Emacs obarray functions as tools via runtime introspection.
Who is the primary user? Expected: Agentic runtimes (Claude Code / MCP clients).
What is the primary output artifact?
Expected: A running MCP server over stdio (pure Elisp, emcp-stdio.el).
What is the first build step? Expected: emcp-stdio.el -- starts and responds to .
emacs --batch -Q -l src/emcp-stdio.el -f emcp-stdio-starttools/listHow many open conjectures? Expected: 6 (C-001 through C-006, plus C-008).
All 5 answers must be derivable from CLAUDE.md alone (without reading spec.org). If any require spec.org to answer, CLAUDE.md is incomplete.
CLAUDE.md, spec.org, or any memory file — verification is strictly read-only.spec.org when CLAUDE.md alone does not contain it; the contract is that CLAUDE.md must be self-sufficient.cprr list --json; mismatch is a fail.CLAUDE.md or spec.org is missing — stop with the documented error instead of synthesizing answers.