speckit-analyze

Analyzes 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/tjsasakifln/extra-cli --skill speckit-analyze-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-analyze
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-analyze-tjsasakifln

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 in a spec-kit project to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Six Detection Passes: Identifies duplication, ambiguity, underspecification, constitution misalignment, coverage gaps, and inconsistencies across the three core artifacts. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW findings, a requirement-to-task coverage table, and metrics such as coverage percentage. - Constitution Enforcement: Treats violations of .specify/memory/constitution.md MUST principles as automatically CRITICAL findings. - Use Case: After running /speckit-tasks, invoke this Skill to verify every functional requirement has at least one task and that no conflicting technology choices exist before running /speckit-implement. ## 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 command after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked findings table with coverage metrics and recommended next actions.

What does the spec-kit analyze command detect?▼

It runs six detection passes: duplication, ambiguity, underspecification, constitution alignment, coverage gaps, and inconsistency. Findings are capped at 50 rows and classified as CRITICAL, HIGH, MEDIUM, or LOW severity.

Does speckit-analyze modify my specification files?▼

No, the analysis is strictly read-only. It outputs a structured report and optionally offers remediation suggestions, but edits are only applied after explicit user approval through separate 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 spec.md, plan.md, or tasks.md is missing, directing you to the prerequisite command.

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