speckit-analyze

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

Updated Jan 28, 2024
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-analyze-thiago-cruz-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Thiago-Cruz-eng/KrockSide/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-analyze-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specification artifacts cause implementation failures. This Skill performs a read-only, cross-artifact analysis of spec.md, plan.md, and tasks.md to detect duplications, ambiguities, underspecification, 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 task coverage and no constitution principle is violated before starting /speckit-implement. ## Quick Start Ask the assistant to run the speckit-analyze command 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?▼

Run the speckit-analyze command after generating tasks.md. It loads spec.md, plan.md, and tasks.md, builds a requirement-to-task coverage map, and outputs a severity-ranked findings table with recommendations.

What does a spec-kit consistency analysis detect?▼

It detects near-duplicate requirements, vague or unmeasurable wording, unresolved placeholders, constitution violations, requirements with zero task coverage, unmapped tasks, terminology drift, and conflicting requirements across artifacts.

When should I run the 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 tasks.md is missing, since coverage analysis requires all three artifacts.

Does the analysis modify my spec or task files?▼

No. The analysis is strictly read-only and only outputs a structured Markdown report. It can offer a remediation plan, but edits are applied only after explicit user approval through separate commands.

Why does the analysis 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 classified as CRITICAL and must be resolved in the spec, plan, or tasks.