speckit-analyze

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-analyze-carl-fabri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Carl-Fabri/TestAngularSpecDriven/tree/main/test-angular/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-analyze-carl-fabri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and uncovered tasks that cause costly rework. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md to surface these issues early. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: 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 coverage percentage 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 on a new feature, run this analysis to receive a structured severity-ranked report with remediation suggestions before invoking /speckit-implement. ## Quick Start Ask the assistant to run the speckit-analyze skill to check the current feature's spec, plan, and tasks for consistency issues and coverage gaps.

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-kit artifacts for inconsistencies before implementation?

Run the speckit-analyze command after /speckit-tasks has produced tasks.md. It loads spec.md, plan.md, and tasks.md, then outputs a structured report of duplications, ambiguities, coverage gaps, and constitution conflicts ranked by severity.

What does the spec-kit analyze command detect?

It detects near-duplicate requirements, vague adjectives lacking measurable criteria, unresolved placeholders, requirements with zero task coverage, unmapped tasks, terminology drift, conflicting requirements, and violations of constitution MUST principles.

Does speckit-analyze modify my spec or task files?

No, the analysis is strictly read-only. It outputs a Markdown report with findings and recommendations, and only offers optional remediation suggestions that require explicit user approval before any follow-up editing commands run.

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

Run it after /speckit-tasks successfully generates a complete tasks.md and before /speckit-implement. It aborts with an error if any required artifact is missing, directing you to the prerequisite command.

Why does speckit-analyze report CRITICAL constitution issues?

The project constitution at .specify/memory/constitution.md is treated as non-negotiable. Any requirement or plan element conflicting with a MUST principle is automatically classified as CRITICAL and must be resolved in the artifacts, not by reinterpreting the principle.