speckit-analyze

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

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-analyze-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-analyze-opsmill

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 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 skill to check consistency and requirement coverage across the current feature's spec, plan, and tasks files.

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, plan, and tasks files?▼

Run the speckit-analyze command after tasks.md has been generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and reports duplications, ambiguities, inconsistencies, and coverage gaps in a structured Markdown report.

When should I run spec analysis in a spec-kit workflow?▼

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. The analysis aborts with an error if any required artifact is missing, directing you to run the prerequisite command first.

Does the analysis modify my spec or tasks files?▼

No, the analysis is strictly read-only and never modifies files. It outputs a report and optionally offers remediation suggestions, but edits are only applied after explicit user approval through separate commands.

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.

Why does the analysis report zero coverage for a requirement?▼

A requirement shows zero coverage when no task in tasks.md maps to it by ID, keyword, or key phrase. Add tasks covering that requirement or refine task descriptions to reference it explicitly.