speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes spec.md, plan.md, and tasks.md to uncover non-destructive inconsistencies, duplications, and gaps after task generation.

Core Features & Use Cases

  • Non-destructive cross-artifact analysis across core spec artifacts.
  • Generates a compact findings report plus a coverage map to guide remediation.
  • Use Case: project teams running spec-kit workflows can validate alignment before implementation.

Quick Start

Run speckit-analyze to generate a cross-artifact analysis 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?

To check for inconsistencies across spec.md, plan.md, and tasks.md, run a cross-artifact analysis to generate a findings table, coverage map, and optional remediation guidance. This validates alignment before implementation.

What is cross-artifact consistency analysis in a spec-kit workflow?

Cross-artifact consistency analysis is a non-destructive validation process that uncovers duplications and gaps across core spec artifacts after task generation. It ensures project teams maintain alignment before implementation begins.

Does spec-kit analysis require a .specify directory?

Yes, spec-kit analysis requires a .specify directory within your project. This directory enforces pre- and post-analysis checks, stores the constitution in .specify/memory/constitution.md, and validates artifact coverage.

Can I automatically fix tasks.md gaps after generating spec artifacts?

You cannot automatically fix gaps, as the analysis is non-destructive and outputs a read-only findings table. However, it provides optional remediation guidance and a coverage summary to help you manually correct tasks.md.

When should I run cross-artifact analysis during spec-kit project development?

You should run cross-artifact analysis immediately after task generation. This timing ensures you uncover non-destructive inconsistencies, duplications, and gaps across spec.md, plan.md, and tasks.md before starting implementation.