Skip to main content
command CX Codex

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

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/speckit.analyze.md
Open on GitHub

What 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.md

Call it with /speckit.analyze. For all projects use ~/.claude/commands/

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.

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →
speckit-baseline dceoy The speckit-baseline skill reads your source files and turns them into a framework-agnostic feature spec with user stories and requirements. Useful when a codebase exists but written requirements do not. CX Codex +1 1,600installs speckit.companion.status alfredoperez speckit.companion.status — a command for Claude Code and Codex reads .spec-context.json and reports the active spec’s step, status, decisions, and next action. It is read-only. CX Codex +1 ★ 110repo stars speckit.companion.resume alfredoperez speckit.companion.resume is a command for Claude Code that resumes spec-driven development after a pause. It carries recorded decisions forward and starts the next pipeline step. CX Codex +1 ★ 110repo stars tlc-spec-lean Tech Leads Club - github.com/tech-leads-club The tlc-spec-lean skill guides feature work from a reviewed plan through evidence-backed checks, implementation, and independent verification. Use it when requirements need to be agreed before coding begins. CX Codex +1 ★ 7,191repo stars speckit-specify github-spec-kit speckit-specify turns a plain-language feature description into a spec folder: short name, number, spec.md from the template, and a path saved in .specify/feature.json. CX Codex +1 2,700installs 03-shadow-areas AI-Driven Dev 03-shadow-areas — a skill that scans written artifacts (ideas, user stories, PRDs, specs) and produces a structured report of blind spots—what the author has not addressed. Runs on Claude Code, Cursor, Codex, GitHub Copilot, and OpenCode. CX Codex +1 ★ 571repo stars

From the same set9

speckit.taskstoissues speckit.taskstoissues converts a list of tasks into dependency-ordered GitHub issues using design artifacts and project context. Works only with GitHub repositories. CX Codex +1 ★ 117repo stars speckit.plan speckit.plan executes implementation planning workflow to produce architectural artifacts and API contracts. CX Codex +1 ★ 117repo stars speckit.constitution The speckit.constitution command edits a project’s constitution and checks related templates and guidance for alignment. Use it when development principles or governance rules change. CX Codex +1 ★ 117repo stars speckit.tasks speckit.tasks builds a tasks.md file for a feature from plan.md and spec.md, splitting work into phases by user story priority. CX Codex +1 ★ 117repo stars speckit.implement The speckit.implement command works through the tasks in tasks.md using the project plan and related documents. Use it to carry out an implementation plan in a defined order. CX Codex +1 ★ 117repo stars speckit.clarify speckit.clarify — a command that scans a feature spec for underspecified areas and asks up to 5 targeted questions to fill gaps before planning begins. CX Codex +1 ★ 117repo stars speckit.specify speckit.specify builds or updates a feature specification straight from a natural language prompt. Handy for structuring requirements and acceptance criteria before writing code. CX Codex +1 ★ 117repo stars speckit.checklist speckit.checklist builds a checklist for reviewing feature requirements, including unclear statements and missing scenarios. Use it before implementing a feature or reviewing its spec. CX Codex +1 ★ 117repo stars

Project sponsors

Companies that keep this analytics open