speckit-analyze

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

Updated May 19, 2026
One-click install
npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-analyze-nasalciuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Nasalciuc/ATS-HERO/tree/main/.cursor/skills/speckit-analyze
Command: npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-analyze-nasalciuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and uncovered tasks that cause 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 Validation: Flags violations of project constitution MUST principles as CRITICAL findings. - Use Case: After running /speckit-tasks on a new feature, run this analysis to receive a severity-ranked report of findings before starting implementation. ## Quick Start Ask the assistant to run the speckit-analyze skill to check the current feature's spec, plan, and tasks for inconsistencies 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 skill after tasks.md has been generated. It performs a read-only analysis across spec.md, plan.md, and tasks.md, producing a severity-ranked report of duplications, ambiguities, coverage gaps, and constitution violations.

What does the specification analysis 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 spec or task files?▼

No, the analysis is strictly read-only. It outputs a structured report and offers an optional remediation plan, but file edits only happen if you explicitly approve and run follow-up commands manually.

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

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. It requires the .specify project structure with spec.md, plan.md, and tasks.md present in the feature directory.

Why does the analysis report CRITICAL findings for constitution conflicts?▼

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 spec, plan, or tasks before implementation.