speckit-analyze

Analyzes 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/KarenTenorio963/curso-mcp-karentenorio --skill speckit-analyze-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill speckit-analyze-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only, cross-artifact analysis of a spec-kit project's spec.md, plan.md, and tasks.md files to detect 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 specification artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting coverage percentage and unmapped tasks. - Severity-Ranked Report: Produces a structured Markdown report with findings classified as CRITICAL, HIGH, MEDIUM, or LOW, plus metrics and next-action recommendations. - Use Case: After running /speckit-tasks on a new feature, run this analysis to confirm every requirement has task coverage and no constitution principle is violated before starting implementation. ## Quick Start Run the speckit-analyze skill to check my spec, plan, and tasks files for inconsistencies and coverage gaps before implementation.

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-kit artifacts for inconsistencies before implementation?▼

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 duplications, ambiguities, coverage gaps, and constitution conflicts 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.

When should I run specification analysis in a spec-kit workflow?▼

Run it only after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. Running it earlier fails because the analysis requires all three artifacts to exist.

Does spec-kit analysis modify my specification files?▼

No, the analysis is strictly read-only. It outputs a structured Markdown report and offers an optional remediation plan, but edits are only applied after explicit user approval through separate commands.

Why does the analyze command fail with a missing file error?▼

The command aborts if spec.md, plan.md, or tasks.md is missing from the feature directory. Run the missing prerequisite command such as /speckit-specify, /speckit-plan, or /speckit-tasks first.