speckit-analyze

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill speckit-analyze-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Powerworks/Underwriting/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/Powerworks/Underwriting --skill speckit-analyze-powerworks

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 to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Six Detection Passes: Identifies duplication, ambiguity, underspecification, constitution misalignment, coverage gaps, and inconsistencies across the three core spec-kit artifacts. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW severity findings, a requirement-to-task coverage table, and metrics. - Extension Hooks: Supports optional and mandatory before/after analysis hooks defined in .specify/extensions.yml. - Use Case: After running /speckit-tasks, invoke this Skill to verify every functional requirement has at least one task and that no plan element violates the project constitution before running /speckit-implement. ## Quick Start Run the speckit-analyze skill to check my spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps 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 spec-kit artifacts for inconsistencies before implementation?▼

Run the speckit-analyze skill after tasks.md has been generated. It performs six detection passes across spec.md, plan.md, and tasks.md, then outputs a severity-ranked report with findings, coverage metrics, and recommended next actions.

What does the spec-kit analyze command detect?▼

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

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

No, the analysis is strictly read-only. It outputs a structured report and offers an optional remediation plan, but file edits only happen if you explicitly approve follow-up commands.

When should I run spec-kit analysis in the 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 the prerequisite command.

Why does speckit-analyze report constitution conflicts 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 classified as CRITICAL and must be resolved in the spec, plan, or tasks.