speckit-analyze

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-analyze-speeddesigns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/speeddesigns/cvusd-calendars/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-analyze-speeddesigns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specification artifacts cause implementation failures. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Consistency Detection: Identifies near-duplicate requirements, terminology drift, conflicting requirements, and task ordering contradictions across the three core artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero coverage and unmapped tasks. - Constitution Validation: Treats violations of the project constitution (.specify/memory/constitution.md) as CRITICAL findings that must be resolved before implementation. - Use Case: After generating tasks.md with speckit-tasks, run this analysis to receive a severity-ranked report with a coverage summary table and concrete remediation suggestions before starting implementation. ## Quick Start Ask the agent to run the speckit-analyze skill to check my 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?

Run the speckit-analyze skill after generating tasks.md. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and outputs a findings table covering duplication, ambiguity, underspecification, inconsistency, and coverage gaps.

When should I run spec-kit analyze in the 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 coverage mapping requires the full task list.

Does speckit-analyze modify my specification files?

No, the analysis is strictly read-only. It outputs a structured Markdown report with findings and an optional remediation plan, but file edits only happen if you explicitly approve follow-up changes.

What counts as a critical issue in spec analysis?

Critical issues include violations of constitution MUST principles, missing core spec artifacts, and requirements with zero task coverage that block baseline functionality. Critical findings should be resolved before running speckit-implement.

Why does the analysis report zero coverage for a requirement?

A requirement shows zero coverage when no task in tasks.md maps to it by ID, keyword, or key phrase. Add tasks addressing that requirement or refine task descriptions to reference it explicitly.