speckit-analyze

Analyzes spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-analyze-msaid1976
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/msaid1976/TSP-SmartAIRoute/tree/main/SmartRouteAI/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-analyze-msaid1976

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specification-driven projects often accumulate inconsistencies between the spec, implementation plan, and task list, leading to uncovered requirements, duplicated work, and constitution violations discovered too late. This Skill performs a read-only cross-artifact audit before implementation begins. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecified requirements, terminology drift, and conflicting requirements across spec.md, plan.md, and tasks.md. - 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 to generate tasks.md, run this analysis to receive a severity-ranked findings report with remediation suggestions before starting /speckit.implement. ## Quick Start Ask the assistant to run the speckit analyze command to audit 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 consistency between spec.md, plan.md, and tasks.md?▼

Run the speckit analyze command after tasks.md has been generated. It loads the three artifacts, builds requirement and task inventories, and outputs a findings table covering duplications, ambiguities, inconsistencies, and coverage gaps.

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. The analysis aborts with an error if tasks.md is missing, since task coverage mapping is a core part of the report.

Does the analysis modify my spec or task files?▼

No, the analysis is strictly read-only and never modifies files. It outputs a structured Markdown report and only offers remediation suggestions, which require explicit user approval before any follow-up editing commands are invoked.

What severity levels does the analysis report use?▼

Findings are classified as CRITICAL, HIGH, MEDIUM, or LOW. Constitution MUST violations and uncovered blocking requirements are CRITICAL, while style and wording issues are LOW. The report caps findings at 50 rows with an overflow summary.

What project structure is required for spec-kit analysis?▼

The project must have a .specify directory containing scripts/bash/check-prerequisites.sh, a memory/constitution.md file, and a feature directory with spec.md, plan.md, and tasks.md. Missing required files cause the analysis to abort with guidance.