speckit-analyze

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-analyze-eovipmak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/eovipmak/unattended-iso/tree/main/.commandcode/skills/speckit-analyze
Command: npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-analyze-eovipmak

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 to detect duplications, ambiguities, underspecified requirements, constitution violations, and coverage gaps before implementation begins. ## Core Features & Use Cases - Consistency Detection: Identifies near-duplicate requirements, terminology drift, conflicting requirements, and task ordering contradictions across the three core artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting requirements with zero coverage and unmapped tasks. - Constitution Validation: Checks artifacts against the project constitution (.specify/memory/constitution.md), flagging MUST-principle violations as CRITICAL. - Use Case: After generating tasks.md with speckit-tasks, run this analysis to receive a severity-ranked findings report with metrics before starting implementation. ## Quick Start Ask the assistant to run a cross-artifact consistency analysis on the current feature's spec.md, plan.md, and tasks.md 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.md, plan.md, and tasks.md?

Run the speckit-analyze command after tasks.md is generated. It loads the three artifacts, builds requirement and task inventories, and outputs a findings table with severity ratings plus a coverage summary mapping requirements to tasks.

What does the spec-kit analyze command detect?

It detects near-duplicate requirements, vague or ambiguous wording, unresolved placeholders, underspecified requirements, constitution violations, requirements with zero task coverage, unmapped tasks, terminology drift, and task ordering contradictions.

Does speckit-analyze modify my specification files?

No, the analysis is strictly read-only. It outputs a structured Markdown report and optionally offers remediation suggestions, but it never edits spec.md, plan.md, tasks.md, or any other file.

When should I run the analyze step in a spec-kit workflow?

Run it after speckit-tasks has produced a complete tasks.md and before speckit-implement. The command aborts with an error if any required artifact is missing, directing you to run the prerequisite command first.

How are findings prioritized in the analysis report?

Findings are assigned CRITICAL, HIGH, MEDIUM, or LOW severity. Constitution MUST violations and uncovered blocking requirements are CRITICAL, duplicates and untestable criteria are HIGH, terminology drift is MEDIUM, and style issues are LOW.