speckit-analyze

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

5|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-analyze-theonlytruebigmac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/theonlytruebigmac/n-central-rest-api-mcp/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-analyze-theonlytruebigmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md in a spec-kit project, detecting duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Six Detection Passes: Identifies duplications, ambiguities, underspecification, constitution misalignment, coverage gaps, and inconsistencies across the three core artifacts. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW severity findings, a requirement-to-task coverage table, and metrics. - Constitution Enforcement: Treats violations of .specify/memory/constitution.md MUST principles as automatically CRITICAL findings. - Use Case: After running task generation on a new feature, invoke this Skill to verify every functional requirement has at least one task and that no conflicting technology choices exist between spec and plan before starting implementation. ## Quick Start Ask the agent 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.md and tasks.md for inconsistencies before implementation?▼

Run the speckit-analyze skill after task generation completes. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked findings report with coverage metrics, all without modifying any files.

What does the spec-kit analyze command detect?▼

It runs six detection passes: duplication, ambiguity (vague terms like fast or secure), underspecification, constitution alignment, coverage gaps (requirements with zero tasks), and inconsistency such as terminology drift or conflicting technology choices.

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

Run it only after tasks.md has been fully generated by the tasks command and before implementation begins. It aborts with an error if spec.md, plan.md, or tasks.md are missing, directing you to run the prerequisite commands first.

Does the analysis 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 edits are only applied if you explicitly approve follow-up commands.

Why are constitution violations flagged as critical in spec analysis?▼

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 assigned CRITICAL severity and must be resolved in the artifacts, not by diluting the principle.