speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent, duplicated, or underspecified requirements across specification artifacts cause implementation failures. This Skill performs a read-only cross-artifact analysis of spec.md, plan.md, and tasks.md to surface inconsistencies, ambiguities, and coverage gaps before coding begins. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: 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 Validation: Flags violations of project constitution MUST principles as CRITICAL findings requiring resolution before implementation. - Use Case: After running /speckit-tasks to generate a task breakdown, run this analysis to verify every requirement has task coverage and no conflicting technology choices exist before invoking /speckit-implement. ## Quick Start Ask the assistant 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 files?▼

Run this analysis after generating tasks.md with /speckit-tasks. It loads the three artifacts, builds requirement and task inventories, and reports duplications, ambiguities, coverage gaps, and inconsistencies in a severity-ranked table.

What does the spec-kit analyze command detect?▼

It detects near-duplicate requirements, vague terms lacking measurable criteria, unresolved placeholders, requirements with zero task coverage, unmapped tasks, terminology drift, conflicting requirements, and constitution principle violations.

Does the analysis modify my spec or tasks files?▼

No, the analysis is strictly read-only. It outputs a structured Markdown report with findings and recommendations, and only offers optional remediation suggestions that require explicit user approval before any edits.

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. Critical findings such as constitution violations or uncovered core requirements should be resolved first.

Why does the 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 file is missing, run the corresponding prerequisite command such as /speckit-specify, /speckit-plan, or /speckit-tasks first.