speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specification artifacts cause implementation failures. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Consistency Detection: Identifies terminology drift, conflicting requirements, and data model mismatches across the three core spec-kit artifacts. - 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 severity findings, metrics, and next-action recommendations. - Use Case: After running task generation in a spec-kit project, invoke this Skill to verify that all requirements have task coverage and no constitution principles are violated before starting implementation. ## Quick Start Run the analyze command 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 has been generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and outputs a severity-ranked findings report with coverage metrics.

What does the spec-kit analyze command detect?

It detects near-duplicate requirements, vague or ambiguous wording, unresolved placeholders, underspecified requirements, constitution violations, terminology drift, conflicting requirements, and requirements lacking task coverage.

Does the analyze command modify my spec or tasks files?

No, the analysis is strictly read-only. It outputs a structured report and optionally suggests remediation edits, but never modifies files. Any fixes require explicit user approval and separate editing commands.

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

Run it after task generation completes and tasks.md exists, but before implementation. It aborts with an error if required artifacts are missing, directing you to run the prerequisite commands first.

Why does analyze report constitution violations as critical?

The project constitution in .specify/memory/constitution.md is treated as non-negotiable. Any requirement or plan element conflicting with a MUST principle is automatically classified as CRITICAL and must be resolved in the artifacts, not the constitution.