speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This analysis tool identifies inconsistencies, ambiguities, and gaps across the spec, plan, and tasks artifacts to improve alignment before implementation.

Core Features & Use Cases

  • Automated cross-artifact consistency checks across spec.md, plan.md, and tasks.md after task generation.
  • Ambiguity and underspecification detection with severity tagging.
  • Constitution alignment verification against the project rules and memory constitutional references.
  • Use Case: Run this analysis after speckit.tasks to surface issues and guide remediation before /speckit.implement.

Quick Start

Run the speckit-analyze command after /speckit.tasks completes to trigger a structured report of cross-artifact issues

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 artifacts?▼

Cross-artifact consistency checks identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md after task generation to improve alignment before implementation.

When do I need to run cross-artifact analysis for my project documentation?▼

Cross-artifact analysis is needed after speckit.tasks successfully produces a complete tasks.md, serving as a read-only verification step to surface issues and guide remediation before the implementation phase begins.

How do I verify if my generated tasks align with project constitution rules?▼

Constitution alignment verification checks your generated tasks.md against the non-negotiable project rules defined in the memory constitution reference at .specify/memory/constitution.md.

Can I automatically fix ambiguities found during spec and plan analysis?▼

The analysis process is strictly read-only and outputs a structured report with severity tagging, but it may propose an optional remediation plan only if you grant explicit user approval.

Does cross-artifact analysis work without a complete tasks.md file?▼

No, cross-artifact analysis must run only after speckit.tasks has successfully produced a complete tasks.md, relying on this output alongside spec.md and plan.md for accurate inconsistency detection.

What is the best way to detect underspecified items before implementation?▼

Ambiguity and underspecification detection with severity tagging scans your spec.md, plan.md, and tasks.md after task generation to surface gaps and guide remediation before implementation begins.