speckit-analyze

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/360org/vuaassistant --skill speckit-analyze-360org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/360org/vuaassistant/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/360org/vuaassistant --skill speckit-analyze-360org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only, cross-artifact analysis of spec.md, plan.md, and tasks.md to detect duplications, ambiguities, underspecified requirements, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects terminology drift, conflicting requirements, and data entities referenced in one artifact but missing from others. - 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 findings, coverage metrics, and next-action recommendations. - Use Case: After running /speckit-tasks on a new feature, run this analysis to confirm every requirement has implementing tasks and no constitution principle is violated before starting /speckit-implement. ## Quick Start Run the speckit-analyze skill to check my spec.md, plan.md, and tasks.md 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 consistency before implementation?▼

Run the speckit-analyze command after tasks.md is generated. 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 spec-kit analyze detect in specification artifacts?▼

It detects near-duplicate requirements, vague terms lacking measurable criteria, unresolved placeholders, constitution violations, requirements with zero task coverage, unmapped tasks, terminology drift, and conflicting requirements across the three core artifacts.

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

No, the analysis is strictly read-only. It outputs a structured Markdown report and optionally suggests remediation edits, but changes are only applied after explicit user approval through separate editing 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 aborts with an error if required artifacts are missing, directing you to run the prerequisite commands first.

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 rated CRITICAL and must be resolved by adjusting the spec, plan, or tasks.