speckit-analyze

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

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/rcmilan/godot-scrabblerabble --skill speckit-analyze-rcmilan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/rcmilan/godot-scrabblerabble/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/rcmilan/godot-scrabblerabble --skill speckit-analyze-rcmilan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-destructively evaluate consistency and quality across spec.md, plan.md, and tasks.md after task generation to surface inconsistencies and ambiguities.

Core Features & Use Cases

  • Cross-artifact analysis: identifies inconsistencies, duplications, ambiguities, and underspecifications across spec.md, plan.md, and tasks.md.
  • Structured report: outputs a structured analysis report with an optional remediation plan.
  • Read-only governance: enforces constitution rules and ensures evaluation happens after tasks.md is complete.

Quick Start

Run the speckit-analyze after speckit.tasks has generated tasks.md to produce the 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, plan, and tasks files?

Cross-artifact analysis evaluates spec.md, plan.md, and tasks.md to identify inconsistencies, duplications, and underspecifications. It produces a structured report with optional remediation guidance to ensure alignment before implementation.

When should I run a cross-artifact quality analysis for my project specs?

You should run cross-artifact quality analysis after speckit.tasks generates a complete tasks.md within your spec-kit project structure. This timing ensures all artifacts exist and are evaluated for consistency before implementation begins.

Can I analyze spec.md and plan.md without a completed tasks.md file?

No, cross-artifact analysis requires a complete tasks.md file to function properly. The evaluation operates after speckit.tasks finishes generation, ensuring all three artifacts exist before analyzing for inconsistencies and ambiguities.

Does cross-artifact analysis modify the spec and tasks files during evaluation?

No, cross-artifact analysis enforces strict read-only governance during evaluation. It loads the constitution as a gating reference and outputs a structured analysis report without modifying your existing spec.md, plan.md, or tasks.md files.

What is cross-artifact analysis and what problem does it solve?

Cross-artifact analysis is a non-destructive evaluation method that identifies inconsistencies, duplications, ambiguities, and underspecifications across spec.md, plan.md, and tasks.md. It solves the problem of misaligned project documents before implementation.

Do I need a constitution file to run spec and task consistency checks?

Yes, spec and task consistency checks require the .specify/memory/constitution.md file to be present as a gating reference. This constitution file is loaded during analysis to enforce governance rules throughout the evaluation process.