speckit-analyze

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

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/marionoratoRN/custom-speckit-flow --skill speckit-analyze-marionoratorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/marionoratoRN/custom-speckit-flow/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/marionoratoRN/custom-speckit-flow --skill speckit-analyze-marionoratorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent specifications, plans, and task lists cause implementation failures that surface too late. This Skill performs a read-only cross-artifact analysis to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before any code is written. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: 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 task coverage and unmapped tasks. - Constitution Enforcement: Treats violations of project constitution MUST principles as CRITICAL findings requiring resolution before implementation. - Use Case: After running /speckit-tasks on a new feature, run this analysis to receive a severity-ranked report showing that a performance success criterion has no corresponding task and that two requirements conflict on framework choice. ## Quick Start Ask the assistant to run the speckit-analyze skill to check the current feature's spec, plan, and tasks for inconsistencies and coverage gaps.

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 and task consistency before implementation?▼

Run the speckit-analyze command after /speckit-tasks completes. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked findings report without modifying any files.

What does the spec-kit analyze command detect?▼

It detects near-duplicate requirements, vague or unmeasurable wording, unresolved placeholders, constitution violations, requirements with zero task coverage, unmapped tasks, terminology drift, and conflicting requirements across the three core artifacts.

When should I run speckit-analyze in the workflow?▼

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. It aborts with an error if spec.md or tasks.md is missing, directing you to run the prerequisite command first.

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 edits are only applied after you explicitly approve and invoke follow-up commands.

How are findings prioritized in the analysis report?▼

Findings are ranked CRITICAL, HIGH, MEDIUM, or LOW. Constitution MUST violations and uncovered blocking requirements are always CRITICAL, while style issues are LOW. The report caps at 50 findings with an overflow summary.