speckit-analyze

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-analyze-magnoalves1993
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/MagnoAlves1993/handy/tree/main/.github/skills/speckit-analyze
Command: npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-analyze-magnoalves1993

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In spec-driven development, inconsistencies between the specification, implementation plan, and task list cause rework and missed requirements. This Skill performs a read-only cross-artifact analysis to detect duplications, ambiguities, underspecified items, coverage gaps, and constitution violations 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 coverage and unmapped tasks. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW findings, coverage metrics, and next-action recommendations. - Use Case: After running /speckit-tasks on a new feature, run this analysis to verify that all functional requirements have implementing tasks and that no plan element violates the project constitution before starting /speckit-implement. ## Quick Start Ask the AI to run the speckit-analyze skill to check consistency and requirement coverage across the current feature's spec, plan, and tasks files.

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 speckit-analyze command after generating tasks.md. It loads spec.md, plan.md, tasks.md, and the project constitution, then reports duplications, ambiguities, coverage gaps, and inconsistencies with severity ratings.

What does the speckit-analyze report include?

The report contains a findings table with severity levels, a requirement-to-task coverage summary, constitution alignment issues, unmapped tasks, and metrics such as total requirements, coverage percentage, and critical issue counts.

Does speckit-analyze modify my specification files?

No, the analysis is strictly read-only. It outputs a structured report and offers an optional remediation plan, but file edits only happen after you explicitly approve and run follow-up commands.

When should I run spec analysis in the SDD workflow?

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. This ensures requirement coverage and constitution compliance are verified before any code is written.

What happens if my project violates a constitution principle?

Constitution conflicts are automatically classified as CRITICAL findings. The constitution is treated as non-negotiable, so the spec, plan, or tasks must be adjusted rather than the principle being diluted or ignored.