speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and duplications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams ensure consistency across spec.md, plan.md, and tasks.md by surfacing gaps, duplications, and ambiguities before implementation.

Core Features & Use Cases

  • Non-destructive cross-artifact analysis across spec.md, plan.md, and tasks.md within a speckit project.
  • Highlights duplications, ambiguities, underspecifications, and coverage gaps to guide remediation.
  • Generates a governance-ready report that supports decision-making and quality gates.

Quick Start

Run speckit-analyze after your tasks.md is generated to produce a findings report.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check for inconsistencies across spec.md, plan.md, and tasks.md?

Cross-artifact analysis identifies inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md by validating alignment against `.specify/memory/constitution.md`. This produces a structured analysis report for quality gates before implementation begins.

When should I run cross-artifact analysis on my speckit project?

Run cross-artifact analysis only after tasks.md is produced within the speckit project. Scoping analysis to this post-generation stage ensures all three artifacts exist for alignment validation against `.specify/memory/constitution.md`.

How does spec plan task alignment validate project governance principles?

Spec plan task alignment validates governance by checking artifact consistency against `.specify/memory/constitution.md`. It generates a governance-ready report highlighting issues, coverage gaps, and recommended remediations for quality gates.

What is the best way to find duplications and ambiguities in specification documents?

Non-destructive cross-artifact analysis finds duplications and ambiguities by comparing spec.md, plan.md, and tasks.md. It highlights underspecifications and coverage gaps to guide remediation before implementation starts.

Does cross-artifact analysis modify my original spec, plan, and tasks files?

Cross-artifact analysis performs non-destructive analysis across spec.md, plan.md, and tasks.md. It produces a structured findings report highlighting issues and recommended remediations without altering source artifacts.