speckit-analyze

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-analyze-zhangliuliuzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/zhangliuliuzhang/memcached-rvv-v2/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-analyze-zhangliuliuzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and uncovered tasks that cause costly rework. This Skill performs a read-only cross-artifact analysis to surface these issues early. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecified requirements, and terminology drift across spec.md, plan.md, and tasks.md. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero coverage and unmapped tasks. - Constitution Validation: Checks artifacts against the project constitution's MUST principles, treating violations as CRITICAL findings. - Use Case: After running /speckit-tasks on a new feature, run this analysis to receive a severity-ranked report with a coverage summary table and remediation suggestions before starting implementation. ## 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.md and tasks.md for inconsistencies before implementation?

Run the speckit-analyze skill after generating tasks.md. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and outputs a severity-ranked findings table with coverage metrics and next-action recommendations.

What does spec-kit analyze detect in specification artifacts?

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.

Does speckit-analyze modify my spec or task files?

No, the analysis is strictly read-only. It outputs a structured Markdown report and optionally offers remediation suggestions, but file edits only happen through separate commands after explicit user approval.

When should I run spec analysis in the 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 spec.md, plan.md, or tasks.md is missing, directing you to the prerequisite command.

Why does speckit-analyze report constitution conflicts as critical?

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