speckit-analyze

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

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/trungenglish/SHOPWISE --skill speckit-analyze-trungenglish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/trungenglish/SHOPWISE/tree/main/.cursor/skills/speckit-analyze
Command: npx skills add https://github.com/trungenglish/SHOPWISE --skill speckit-analyze-trungenglish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain duplications, ambiguities, coverage gaps, and contradictions that cause rework later. 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 on a new feature, run this analysis to get a severity-ranked report with a coverage summary table and concrete next actions before starting /speckit-implement. ## Quick Start Ask the AI to run a cross-artifact consistency and coverage analysis on the current feature's spec.md, plan.md, and tasks.md and report any critical issues.

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 analyze command after tasks.md has been generated. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked findings table with coverage metrics and recommended next actions.

What does the spec-kit analyze command detect?▼

It detects near-duplicate requirements, vague or unmeasurable wording, unresolved placeholders, underspecified requirements, terminology drift, conflicting requirements, tasks with no mapped requirement, and requirements with zero task coverage.

Does the analysis modify my spec or task files?▼

No, the analysis is strictly read-only. It outputs a structured Markdown report and only offers an optional remediation plan, which requires explicit user approval before any follow-up editing commands are invoked.

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

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. The command aborts with an error if any required artifact is missing and tells you which prerequisite command to run.

How are constitution violations handled during 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 classified as CRITICAL and must be resolved in the spec, plan, or tasks.