speckit-analyze

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-analyze-acarmonag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/acarmonag/fullstack-devops-agent-aws-terraform/tree/main/codebase/rdicidr-0.1.0/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-analyze-acarmonag

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, 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 severity 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 implementation. ## Quick Start Ask the assistant to run a consistency analysis across the spec, plan, and tasks artifacts for the current feature before implementation.

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 analysis after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, then reports duplications, ambiguities, inconsistencies, and coverage gaps in a severity-ranked table.

What is spec-kit analyze used for?▼

It validates that generated specification artifacts are internally consistent and complete before implementation. It maps requirements to tasks, checks constitution alignment, and outputs metrics like coverage percentage and critical issue counts.

Does the analysis modify my spec or tasks files?▼

No, the analysis is strictly read-only. It outputs a structured report and optionally suggests remediation edits, but never modifies files; any fixes require explicit user approval and separate commands.

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. It aborts with an error if required artifacts are missing, directing you to run the prerequisite commands first.

What happens when constitution violations are found?▼

Constitution conflicts are automatically classified as CRITICAL findings. The report recommends adjusting the spec, plan, or tasks to comply, since constitution principles are treated as non-negotiable within the analysis scope.