speckit-analyze

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

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ins-enco/ctm__affiliate_backend --skill speckit-analyze-ins-enco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/ins-enco/ctm__affiliate_backend/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/ins-enco/ctm__affiliate_backend --skill speckit-analyze-ins-enco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify inconsistencies, ambiguities, duplications, and coverage gaps across spec.md, plan.md, and tasks.md before implementation so teams catch blocking issues and constitution violations early in the workflow. The analysis is strictly read-only and prioritizes constitution MUSTs, measurable success criteria, and task coverage for requirements.

Core Features & Use Cases

  • Read-only cross-artifact analysis: Parses spec, plan, and tasks to map requirements, user stories, and tasks without modifying repository files.
  • Constitution validation: Loads the project constitution to surface any direct conflicts as CRITICAL issues.
  • Compact, actionable report: Produces a severity-labeled Markdown findings table, coverage summary, unmapped tasks list, and concise next actions for remediation.
  • Use Case: Run after speckit.tasks produces tasks.md to verify that every functional requirement and buildable success criterion has task coverage and that terminology and file references are consistent.

Quick Start

Run speckit-analyze on the feature directory to produce a compact Markdown analysis of spec.md, plan.md, and tasks.md.

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 across spec.md, plan.md, and tasks.md?

Cross-artifact spec consistency analysis identifies inconsistencies, ambiguities, duplications, and coverage gaps across spec.md, plan.md, and tasks.md by parsing frontmatter, mapping FR-/SC- identifiers, and validating constitution rules to emit a severity-labeled Markdown report.

How do I validate constitution rules and task coverage for requirements?

To validate constitution rules and task coverage for requirements, load the project constitution to surface direct conflicts as CRITICAL issues, then verify that every functional requirement and buildable success criterion has corresponding task coverage in the generated tasks.md.

Can I run spec analysis without modifying my repository files?

Yes, you can run spec analysis without modifying repository files because the cross-artifact consistency check operates strictly in read-only mode, parsing the .specify/ directory and artifact sections to produce a non-destructive analysis report.

What is the best way to trace requirements and identify coverage gaps in a spec-kit project?

The best way to trace requirements and identify coverage gaps in a spec-kit project is to map FR-/SC- identifiers across spec, plan, and tasks artifacts to validate measurable success criteria and generate an unmapped tasks list for remediation.

When should I run a cross-artifact consistency audit in the spec-kit workflow?

You should run a cross-artifact consistency audit in the spec-kit workflow immediately after the speckit.tasks task generator produces tasks.md, allowing you to catch blocking issues and constitution violations early before implementation begins.

Why are some tasks unmapped during requirements tracing in spec-kit?

Tasks appear unmapped during requirements tracing in spec-kit when the generated tasks.md contains entries that lack corresponding functional requirements or buildable success criteria in spec.md, which the analysis surfaces in an unmapped tasks list for review.