speckit-analyze

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-analyze-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/speckit-analyze
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-analyze-base-analitica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only, cross-artifact analysis of spec.md, plan.md, and tasks.md to detect duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Consistency Detection: Identifies near-duplicate requirements, terminology drift, conflicting requirements, and task ordering contradictions across the three core artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero 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 report with a coverage summary table and concrete remediation suggestions before starting implementation. ## Quick Start Ask the assistant to run the speckit-analyze skill to check my 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 consistency before implementation?▼

Run the analysis after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, then reports duplications, ambiguities, coverage gaps, and constitution violations with severity ratings.

What does the specification analysis report include?▼

The report contains a findings table with ID, category, severity, location, and recommendation, plus a requirement-to-task coverage summary, constitution alignment issues, unmapped tasks, and metrics like coverage percentage and critical issue count.

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 after you explicitly approve and run follow-up commands.

When should I run the cross-artifact analysis?▼

Run it after task generation completes and before implementation begins. It requires spec.md, plan.md, and a complete tasks.md in the feature directory, and aborts with an error if any required file is missing.

What are the limitations of the consistency analysis?▼

Findings are capped at 50 entries with overflow summarized, and task-to-requirement mapping relies on keyword and ID inference, which may miss implicit relationships. It cannot validate whether the plan is technically sound, only whether artifacts are internally consistent.