speckit-analyze

Analyzes spec.md, plan.md, and tasks.md for inconsistencies, gaps, and constitution violations.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-analyze-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-analyze-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, inconsistencies between a feature's specification, technical plan, and task list can cause wasted effort and broken builds. This Skill performs a read-only cross-artifact analysis that catches duplications, ambiguities, coverage gaps, and constitution conflicts early. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecified requirements, terminology drift, and conflicting requirements across spec.md, plan.md, and tasks.md. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting coverage percentage and unmapped tasks. - Constitution Enforcement: Validates artifacts against the project constitution (.specify/memory/constitution.md), treating MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit-tasks on a new feature, run this analysis to receive a severity-ranked report of findings and concrete remediation suggestions before spending tokens on implementation. ## Quick Start Ask the assistant to run a cross-artifact consistency analysis on the current feature's spec, plan, and tasks 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 consistency between spec, plan, and tasks in spec-kit?

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 reports duplications, ambiguities, coverage gaps, and inconsistencies 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 constitution MUST-principle violations.

Does the analysis modify my spec or task files?

No, the analysis is strictly read-only. It outputs a structured Markdown report with findings and an optional remediation plan, but never edits files. Any fixes require explicit user approval and separate commands.

When should I run cross-artifact analysis in a spec-driven workflow?

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. Running it earlier fails because tasks.md is required; running it later wastes implementation effort on inconsistent artifacts.

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 corresponding prerequisite command (specify, plan, or tasks) to generate the missing artifact first.