speckit-analyze

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

Updated Dec 12, 2024
One-click install
npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-analyze-kipariss1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/kipariss1/czech_out_auto_bot/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-analyze-kipariss1

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 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 - 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 tables, and metrics, capped at 50 findings. - Use Case: After running /speckit-tasks on a feature, invoke this Skill to verify that all requirements have task coverage and no constitution principles are violated before starting implementation. ## Quick Start Ask the assistant to run the speckit-analyze skill to check consistency across spec.md, plan.md, and tasks.md in the current spec-kit project.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check consistency between spec.md, plan.md, and tasks.md?▼

Run the speckit-analyze skill after generating tasks.md. It loads the three artifacts, builds requirement and task inventories, and reports duplications, ambiguities, inconsistencies, and coverage gaps in a severity-ranked Markdown table.

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. The analysis aborts with an error if spec.md or tasks.md is missing, directing you to run the prerequisite commands first.

Does speckit-analyze modify my specification 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 invoke follow-up commands manually.

What counts as a critical issue in spec analysis?▼

Critical issues include violations of constitution MUST principles, missing core spec artifacts, and requirements with zero task coverage that block baseline functionality. Constitution conflicts always take priority and cannot be diluted or ignored.

Why does the analysis report stop at 50 findings?▼

The report caps findings at 50 to keep output token-efficient and high-signal. Remaining findings are aggregated into an overflow summary so the report stays actionable without losing visibility into issue counts.