speckit-analyze

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

Updated May 28, 2026
One-click install
npx skills add https://github.com/whw23/PingoGate --skill speckit-analyze-whw23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/whw23/PingoGate/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/whw23/PingoGate --skill speckit-analyze-whw23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and uncovered tasks that cause costly rework. This Skill performs a read-only cross-artifact analysis of spec.md, plan.md, and tasks.md to surface these issues early. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecified requirements, terminology drift, and conflicting requirements across the three core spec-kit artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting coverage percentage and unmapped tasks. - Constitution Enforcement: Validates artifacts against the project constitution (.specify/memory/constitution.md), treating MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit-tasks on a new feature, run this analysis to receive a severity-ranked report with a findings table, coverage summary, and concrete next-action recommendations before starting implementation. ## Quick Start Ask the AI to run a cross-artifact consistency analysis on the current feature's spec, plan, and tasks files and report any critical issues.

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 consistency before implementation?▼

Run the analysis after generating tasks.md to detect inconsistencies, duplications, ambiguities, and coverage gaps across spec.md, plan.md, and tasks.md. It outputs a severity-ranked findings table with recommendations for each issue.

What does a requirements coverage analysis report include?▼

The report includes a findings table with severity ratings, a coverage summary mapping requirements to task IDs, constitution alignment issues, unmapped tasks, and metrics such as total requirements, coverage percentage, and critical issue counts.

Does the analysis modify my spec or task files?▼

No, the analysis is strictly read-only and never modifies any files. It outputs a structured report and only offers an optional remediation plan that requires explicit user approval before any follow-up editing commands.

When should I run cross-artifact analysis in spec-kit?▼

Run it only after /speckit-tasks has produced a complete tasks.md, since the analysis requires all three artifacts. It aborts with an error if any required file is missing and instructs you to run the prerequisite command.

What counts as a critical issue in specification analysis?▼

Critical issues include violations of constitution MUST principles, missing core spec artifacts, and requirements with zero task coverage that block baseline functionality. Critical findings should be resolved before proceeding to implementation.