speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies, gaps, and constitution violations.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-analyze-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-analyze-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and coverage gaps that cause rework. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md so teams catch these issues early. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects duplications, ambiguities, underspecified requirements, terminology drift, and conflicting requirements across the three core spec-kit artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting requirements with zero task coverage and unmapped tasks. - Constitution Enforcement: Validates artifacts against the project constitution (.specify/memory/constitution.md), treating MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit-tasks, a team lead runs this analysis and receives a severity-ranked report showing that a performance requirement has no implementing task and that two requirements conflict on framework choice, before any code is written. ## Quick Start Run /speckit-analyze after task generation to produce a read-only consistency and coverage report for the current feature's spec, plan, and tasks.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check spec.md and tasks.md for inconsistencies before implementation?

Run /speckit-analyze after task generation. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked report of duplications, ambiguities, coverage gaps, and conflicts without modifying any files.

What does the speckit-analyze report include?

The report contains a findings table with severity levels (CRITICAL, HIGH, MEDIUM, LOW), a requirement-to-task coverage summary, constitution alignment issues, unmapped tasks, and metrics such as total requirements, coverage percentage, and ambiguity counts.

Does speckit-analyze modify my specification files?

No. The analysis is strictly read-only. It outputs a structured report and offers an optional remediation plan, but concrete edits are only suggested and require explicit user approval and separate follow-up commands.

When should I run spec analysis in a spec-kit workflow?

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. It aborts with an error if required artifacts are missing, directing you to run the prerequisite commands first.

How are constitution violations handled during analysis?

Conflicts with MUST principles in .specify/memory/constitution.md are automatically classified as CRITICAL findings. The constitution is treated as non-negotiable, so the spec, plan, or tasks must be adjusted rather than the principle.