speckit-analyze

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

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-analyze-desarrolloainia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/desarrolloainia/nuevo_circuito_mir/tree/main/backend/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-analyze-desarrolloainia

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 to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects terminology drift, conflicting requirements, and data entities referenced in one artifact but missing from others. - 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 findings, coverage metrics, and next-action recommendations. - Use Case: After running /speckit-tasks, invoke this Skill to verify that all requirements in spec.md are covered by tasks.md and that no plan element violates the project constitution before starting implementation. ## Quick Start Ask the AI to run a consistency and coverage analysis across the spec, plan, and tasks artifacts 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 consistency between spec, plan, and tasks files?▼

Run the speckit-analyze command after tasks.md is 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 structured Markdown report.

How to find requirements with no task coverage in spec-kit?▼

The analysis maps each functional requirement (FR-###) and success criterion (SC-###) to tasks by keyword and explicit reference patterns. Requirements with zero associated tasks appear in the coverage summary table, with CRITICAL severity if they block baseline functionality.

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 if you explicitly approve follow-up commands such as /speckit-specify or /speckit-plan.

When should I run spec 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, instructing you to run the prerequisite command first.

What happens when a requirement violates the project constitution?▼

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