speckit.analyze — Claude Code command: what it does, how to install
speckit.analyze inspects spec.md, plan.md, and tasks.md for conflicts, gaps, and constitution violations before code generation. Runs in read-only mode.
no license ★ 117 updated 2026-10-29
.claude/commands/speckit.analyze.mdWhat speckit.analyze does
The command evaluates consistency across a feature's specification, architectural plan, and task backlog. It is intended to run right after /speckit.tasks generates tasks.md. It extracts requirement slugs, maps them to planned tasks, and verifies constraints against .specify/memory/constitution.md.
The generated review highlights vocabulary drift, missing acceptance criteria, orphaned tasks, and conflicts with constitutional rules. Any contradiction with mandatory project principles is tagged as critical. Findings are capped at 50 table rows to keep token consumption low.
File modifications are completely locked out during execution. You get an inspection breakdown and optional remediation guidance instead. The process fails immediately if .specify/scripts/bash/check-prerequisites.sh or any of the three core documents are missing.
What it helps with
- detect inconsistencies between specification, plan, and task files
- spot functional requirements missing execution tasks
- catch violations against mandatory rules in constitution.md
- flag ambiguous wording and lingering placeholder tokens
Example prompts for the agent
- /speckit.analyze
- /speckit.analyze "focus on auth module"
How to install speckit.analyze
Manually: put the files in place
.claude/commands/speckit.analyze.mdCall it with /speckit.analyze. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/speckit.analyze.mdCall it with /prompts:speckit.analyze. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/speckit.analyze.prompt.mdManually: put the files in place
.gemini/commands/speckit.analyze.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about speckit.analyze
How do I install speckit.analyze in Claude Code?
Place the command definition file at .claude/commands/speckit.analyze.md.
What does speckit.analyze do?
It audits spec.md, plan.md, and tasks.md side by side, reporting broken coverage, vague terms, and architectural conflicts before you begin coding.
Does speckit.analyze edit project documentation automatically?
No, it operates strictly in read-only mode. It outputs a Markdown summary and can propose potential fixes, but it never alters your files directly.