speckit-analyze

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-analyze-alidotcom2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/alidotcom2000/RSSFeedReader/tree/main/.github/skills/speckit-analyze
Command: npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-analyze-alidotcom2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain duplications, ambiguities, coverage gaps, and contradictions that cause costly rework. This Skill performs a read-only cross-artifact consistency analysis so teams catch specification defects early. ## Core Features & Use Cases - Cross-Artifact Analysis: Detects duplications, ambiguities, underspecification, inconsistencies, and coverage gaps across spec.md, plan.md, and tasks.md. - Constitution Enforcement: Validates artifacts against the project constitution (.specify/memory/constitution.md), flagging MUST-principle violations as CRITICAL. - Structured Report: Produces a severity-ranked findings table, requirement-to-task coverage summary, and metrics without modifying any files. - Use Case: After running /speckit-tasks, run this analysis to confirm every functional requirement has task coverage and no conflicting technology choices exist before invoking /speckit-implement. ## Quick Start Ask the AI to run the speckit-analyze skill to check my spec, plan, and tasks 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.md and tasks.md for inconsistencies before implementation?

Run the speckit-analyze skill after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked findings report covering duplications, ambiguities, and coverage gaps.

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, terminology drift, conflicting requirements, and constitution MUST-principle violations.

Does speckit-analyze modify my spec or task files?

No, the analysis is strictly read-only. It outputs a structured Markdown report and offers an optional remediation plan, but file edits only happen after you explicitly approve and run follow-up commands.

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. It requires a spec-kit project structure with the .specify/ directory and aborts if required artifacts are missing.

Why does the analysis report CRITICAL issues for constitution conflicts?

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 rated CRITICAL and must be resolved in the artifacts, not by diluting the principle.