speckit-analyze

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

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/PanyaPrimal/selfHandlerApp --skill speckit-analyze-panyaprimal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/PanyaPrimal/selfHandlerApp/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/PanyaPrimal/selfHandlerApp --skill speckit-analyze-panyaprimal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In spec-driven development, inconsistencies between the specification, implementation plan, and task list often surface only during coding, causing rework. This Skill performs a read-only cross-artifact analysis before implementation begins, catching duplications, ambiguities, coverage gaps, and constitution violations early. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects duplication, ambiguity, underspecification, terminology drift, and conflicting requirements across spec.md, plan.md, and tasks.md. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting requirements with zero task coverage and unmapped tasks. - Constitution Enforcement: Validates artifacts against the project constitution, treating MUST-principle violations as CRITICAL findings. - Use Case: After generating tasks.md with speckit-tasks, run this analysis to receive a severity-ranked findings table, coverage summary, and metrics before starting implementation. ## Quick Start Ask the assistant to run the speckit-analyze skill to check the current feature's spec, plan, and tasks for inconsistencies and coverage gaps.

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.md and tasks.md for inconsistencies before implementation?

Run the speckit-analyze skill after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and outputs a findings table with severity ratings, coverage percentages, and recommended next actions.

What does spec-kit analyze detect in specification artifacts?

It detects near-duplicate requirements, vague adjectives lacking measurable criteria, unresolved placeholders, requirements with zero task coverage, unmapped tasks, terminology drift, conflicting requirements, and violations of constitution MUST principles.

When should I run speckit-analyze 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 tasks.md is missing, since coverage analysis requires the full task list.

Does speckit-analyze modify my spec or task files?

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

Why does speckit-analyze 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 classified CRITICAL and must be resolved by adjusting the spec, plan, or tasks.