speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In spec-driven development, inconsistencies between the specification, implementation plan, and task list cause rework and missed requirements. This Skill performs a read-only cross-artifact analysis that surfaces duplications, ambiguities, underspecifications, constitution violations, and coverage gaps before implementation begins. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: 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 feature, run this analysis to confirm every requirement has implementing tasks and no constitution principle is violated before starting /speckit-implement. ## Quick Start Ask the assistant to run the speckit-analyze skill to check consistency across spec.md, plan.md, and tasks.md for the current feature.

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 in spec-kit?▼

Run the speckit-analyze skill after /speckit-tasks completes. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and reports duplications, ambiguities, inconsistencies, and coverage gaps in a severity-ranked table.

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

Run it after tasks.md has been fully generated and before starting implementation. The analysis aborts if tasks.md is missing, since its coverage mapping depends on a complete task list.

Does speckit-analyze modify my spec or task files?▼

No. The analysis is strictly read-only and never modifies files. It outputs a structured report and optionally suggests remediation edits, which are only applied after explicit user approval through separate commands.

What counts as a critical issue in spec 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 running /speckit-implement.

Why does spec analysis fail with a missing file error?▼

The skill requires spec.md, plan.md, and tasks.md in the feature directory, located via the check-prerequisites script. If any file is missing, it aborts and instructs you to run the prerequisite command that produces it.