speckit-analyze

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

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill speckit-analyze-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill speckit-analyze-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specification-driven projects often drift out of sync: requirements lack tasks, plans contradict specs, and vague wording slips into implementation. This Skill performs a read-only consistency and quality audit across the three core spec-kit artifacts before coding begins. ## 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, flagging MUST-principle violations as CRITICAL findings. - Structured Report: Produces a severity-ranked findings table, requirement-to-task coverage summary, and metrics with concrete next-action recommendations. - Use Case: After running /speckit-tasks, invoke this Skill to verify every functional requirement has at least one task and no conflicting stack choices exist before starting /speckit-implement. ## Quick Start Run the speckit-analyze skill to check my current feature's spec, plan, and tasks files for inconsistencies and missing requirement coverage.

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 speckit-analyze after /speckit-tasks completes. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked report of duplications, ambiguities, and coverage gaps without modifying any files.

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

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

Run it only after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. It aborts with an error if spec.md, plan.md, or tasks.md is missing, directing you to the prerequisite command.

Does speckit-analyze modify my spec or tasks files?▼

No, it is strictly read-only. It outputs a structured analysis report and offers an optional remediation plan, but edits are only applied after you explicitly approve and invoke follow-up commands manually.

Why does speckit-analyze report constitution violations 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 CRITICAL and requires adjusting the spec, plan, or tasks rather than reinterpreting the principle.