speckit-analyze

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

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

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 surface duplications, ambiguities, underspecified requirements, 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 implementation. ## Quick Start Ask the assistant to run a consistency analysis across 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 and task consistency before implementation?▼

Run the analyze command after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked report of inconsistencies, ambiguities, and coverage gaps without modifying any files.

What does the spec-kit analyze command detect?▼

It detects near-duplicate requirements, vague or unmeasurable wording, unresolved placeholders, constitution violations, requirements with zero task coverage, unmapped tasks, terminology drift, and conflicting requirements across the three core artifacts.

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 spec.md, plan.md, or tasks.md is missing, directing you to the prerequisite command.

Does the analysis modify my spec or task files?▼

No. The analysis is strictly read-only and only outputs a structured report. It can offer remediation suggestions for top issues, but edits are never applied automatically and require your explicit approval through separate commands.

Why does the analysis report constitution violations as critical?▼

The project constitution at .specify/memory/constitution.md is treated as non-negotiable. Any requirement or plan element conflicting with a MUST principle is automatically rated CRITICAL and must be resolved by adjusting the spec, plan, or tasks.