speckit-analyze

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-analyze-damian-garces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/damian-garces/spec-driven-development/tree/main/spec-driven-project/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-analyze-damian-garces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In spec-driven development, inconsistencies between the specification, implementation plan, and task list cause rework and defects. This Skill performs a read-only cross-artifact analysis to detect duplications, ambiguities, underspecified requirements, constitution violations, and coverage gaps before implementation begins. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects terminology drift, conflicting requirements, and data model mismatches across spec.md, plan.md, and tasks.md. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero task coverage and unmapped tasks. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW severity findings, metrics, and next-action recommendations. - Use Case: After running /speckit-tasks on a feature, invoke this Skill to verify that all requirements are covered by tasks and that the plan does not violate the project constitution before starting implementation. ## Quick Start Ask the agent to run a consistency analysis across the current feature's spec, plan, and tasks files 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 consistency between spec, plan, and tasks in spec-kit?

Run the analyze command after tasks.md has been generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and reports duplications, ambiguities, inconsistencies, and coverage gaps in a severity-ranked table.

When should I run spec-kit analysis 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 spec.md or tasks.md is missing, directing you to run the prerequisite commands first.

Does the spec-kit analyze command modify my files?

No, the analysis is strictly read-only. It outputs a structured Markdown report with findings and an optional remediation plan, but any edits must be explicitly approved and applied through separate commands.

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. Constitution conflicts are always treated as critical and cannot be diluted.

Why does spec-kit analysis fail with a missing file error?

The analysis requires spec.md, plan.md, and tasks.md in the feature directory, located via the check-prerequisites script. If any required file is missing, it aborts and instructs you to run the corresponding prerequisite command such as /speckit-specify or /speckit-tasks.