speckit-analyze

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

32|9|Updated Feb 2, 2024
One-click install
npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-analyze-esri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Esri/arcgis-gitops/tree/main/.github/skills/speckit-analyze
Command: npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-analyze-esri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md in a spec-kit project to detect duplications, ambiguities, underspecified requirements, constitution violations, and coverage gaps before implementation begins. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects terminology drift, conflicting requirements, and data model mismatches across the three core spec-kit artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting requirements with zero task coverage and unmapped tasks. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW severity findings, coverage metrics, and next-action recommendations. - Use Case: After running /speckit-tasks, invoke this Skill to verify that all requirements in spec.md are covered by tasks.md and that no constitution principles are violated before starting implementation. ## Quick Start Ask the AI to run a consistency and coverage analysis across spec.md, plan.md, and tasks.md in your spec-kit project.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check consistency between spec.md and tasks.md?

Run this analysis after task generation to map each functional requirement and success criterion in spec.md to tasks in tasks.md. It reports requirements with zero task coverage, unmapped tasks, and conflicting or duplicated requirements in a severity-ranked table.

What does the spec-kit analyze command detect?

It detects near-duplicate requirements, vague or ambiguous wording, unresolved placeholders, underspecified requirements, constitution violations, terminology drift, coverage gaps, and task ordering contradictions across spec.md, plan.md, and tasks.md.

Does the analysis modify my specification files?

No, the analysis is strictly read-only and never modifies any files. It outputs a structured Markdown report and optionally offers remediation suggestions that require explicit user approval before any follow-up edits.

When should I run the spec-kit analysis in my workflow?

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. It requires the .specify project structure with spec.md, plan.md, tasks.md, and constitution.md present.

What happens if my project constitution conflicts with a requirement?

Constitution conflicts are automatically classified as CRITICAL findings. The constitution is treated as non-negotiable, so the report recommends adjusting the spec, plan, or tasks rather than weakening the principle.