speckit-analyze

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

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-analyze-andyrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/AndyRace/heart-rate-graph/tree/main/.github/skills/speckit-analyze
Command: npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-analyze-andyrace

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 - Cross-Artifact Consistency Analysis: Detects terminology drift, conflicting requirements, and data model mismatches across the three core spec-kit artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting coverage percentage and unmapped tasks. - Constitution Validation: Flags violations of project constitution MUST principles as CRITICAL findings. - Use Case: After running /speckit-tasks, run this analysis to verify that all requirements have task coverage and no constitution conflicts exist before invoking /speckit-implement. ## Quick Start Ask the AI to run a consistency and coverage analysis across the spec, plan, and tasks files for the current feature.

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 consistency before implementation in spec-kit?

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

What does the spec-kit analyze command detect?

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

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. It aborts with an error if spec.md, plan.md, or tasks.md is missing, directing you to run the prerequisite command first.

Why are constitution conflicts marked as critical issues?

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 CRITICAL and must be resolved by adjusting the spec, plan, or tasks.