speckit-analyze

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

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-analyze-lluisfont
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/lluisfont/clickup-reporting/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-analyze-lluisfont

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specification-driven projects often drift out of sync: requirements lack tasks, plans contradict specs, and vague wording slips into implementation. This Skill performs a read-only, cross-artifact consistency audit across spec.md, plan.md, and tasks.md before coding begins, surfacing duplications, ambiguities, coverage gaps, and constitution violations in one structured report. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecification, terminology drift, and conflicting requirements across the three core Spec Kit artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting coverage percentage 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 the Spec Kit workflow, run this analysis to confirm every requirement has task coverage and no constitution conflicts exist before starting implementation. ## Quick Start Ask the agent to run the speckit-analyze skill to audit 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 a requirements-to-task coverage map, and outputs a severity-ranked findings table with metrics like coverage percentage and ambiguity count.

What does the Spec Kit analyze command detect?

It detects six categories of issues: duplication, ambiguity, underspecification, constitution misalignment, coverage gaps, and inconsistency across artifacts. Findings are capped at 50 rows and assigned CRITICAL, HIGH, MEDIUM, or LOW severity.

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 file edits only happen if you explicitly approve and run follow-up commands.

When should I run spec analysis in the Spec Kit workflow?

Run it after tasks.md has been fully generated by the tasks command and before starting implementation. It requires spec.md, plan.md, and tasks.md to exist, and aborts with an error if any prerequisite artifact is missing.

How are constitution violations handled during analysis?

Any requirement or plan element conflicting with a MUST principle in .specify/memory/constitution.md is automatically classified as CRITICAL. The constitution cannot be diluted or reinterpreted during analysis; changing a principle requires a separate explicit update.