speckit.analyze

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

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill speckit-analyze-jaimejunr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.analyze
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/speckit/speckit.analyze
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill speckit-analyze-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation to surface gaps and ambiguities before implementation.

Core Features & Use Cases

  • Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md.
  • Create a structured analysis report with actionable remediation guidance that can feed into /speckit.implement.
  • Validate alignment with the project constitution and highlight coverage gaps between requirements, tasks, and user stories.

Quick Start

Run speckit.analyze to produce a structured report from 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, plan, and tasks files for inconsistencies before implementation?

To check spec, plan, and tasks files for inconsistencies, run a cross-artifact analysis that identifies duplications, ambiguities, and underspecified items. This non-destructive process surfaces gaps across spec.md, plan.md, and tasks.md without modifying your source files.

What is cross-artifact consistency analysis in software specification?

Cross-artifact consistency analysis is a validation mechanism that detects coverage gaps between requirements, tasks, and user stories. It aligns your project constitution with spec.md, plan.md, and tasks.md to ensure structural quality before implementation begins.

When do I need to analyze tasks.md for ambiguities and duplications?

You need to analyze tasks.md for ambiguities and duplications only after a complete tasks.md is generated. Running the analysis at this stage ensures all three artifacts exist, allowing a thorough cross-reference check to identify underspecified items.

Can I generate a remediation plan without modifying my source spec files?

Yes, you can generate a remediation plan without modifying source spec files. The analysis outputs a structured report with actionable remediation guidance that feeds into implementation, ensuring your original spec.md, plan.md, and tasks.md remain untouched.

Does cross-artifact analysis validate alignment with the project constitution?

Yes, cross-artifact analysis validates alignment with the project constitution. It highlights coverage gaps between requirements, tasks, and user stories across spec.md, plan.md, and tasks.md to ensure your implementation follows constitutional guidelines.