speckit-analyze

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/brianpunzalan/webui-rubric --skill speckit-analyze-brianpunzalan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/brianpunzalan/webui-rubric/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/brianpunzalan/webui-rubric --skill speckit-analyze-brianpunzalan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

speckit-analyze helps you catch inconsistencies, duplications, ambiguities, and missing coverage across your spec, plan, and tasks before you start implementing.

Core Features & Use Cases

  • Cross-artifact consistency checking across spec.md, plan.md, and tasks.md after tasks have been generated.
  • Detects duplication, ambiguity, underspecification, constitution alignment issues, coverage gaps, and ordering/integration inconsistencies.
  • Produces a compact, machine-readable-friendly Markdown report with a prioritized finding table and a coverage summary.

Quick Start

Ask the agent to run the speckit-analyze command after completing tasks generation to produce an analysis report of your spec/plan/tasks alignment.

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

To check consistency across spec.md, plan.md, and tasks.md, perform a cross-artifact analysis to detect duplications, ambiguities, underspecification, and coverage gaps. This read-only process loads the constitution for MUST/SHOULD validation and emits a structured Markdown analysis report.

What is cross-artifact consistency checking in a specification workflow?

Cross-artifact consistency checking validates alignment between your specification, plan, and tasks documents. It identifies duplications, ambiguities, underspecification, constitution conflicts, and coverage gaps, producing a prioritized findings table and coverage summary.

How do I validate task coverage against my project constitution and specification?

Validate task coverage against your project constitution by loading MUST/SHOULD validation rules and building internal requirement-to-task mappings. This identifies coverage gaps and constitution alignment issues across your specification artifacts without modifying files.

Does spec analysis modify my existing markdown files during validation?

Spec analysis does not modify your existing markdown files. It enforces strictly read-only operations during the consistency and quality analysis, ensuring your spec.md, plan.md, and tasks.md remain untouched while generating a separate analysis report.

When should I run a specification and task coverage analysis in my workflow?

Run specification and task coverage analysis after successfully generating a complete tasks.md within your project directory structure. This ensures your spec, plan, and tasks are fully aligned and any integration inconsistencies are caught before implementation begins.

What is the maximum number of findings generated during a spec quality analysis?

The maximum number of findings generated during a spec quality analysis is limited to 50. This constraint ensures the resulting Markdown report remains compact, prioritized, and manageable for reviewing cross-artifact inconsistencies and coverage gaps.