speckit-analyze

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

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/victorevh/orbitarium-engine-sdd --skill speckit-analyze-victorevh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/victorevh/orbitarium-engine-sdd/tree/main/.cursor/skills/speckit-analyze
Command: npx skills add https://github.com/victorevh/orbitarium-engine-sdd --skill speckit-analyze-victorevh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md to improve alignment before implementation.

Core Features & Use Cases

  • Cross-artifact consistency checks across spec.md, plan.md, and tasks.md to surface conflicts.
  • Non-destructive analysis in read-only mode that does not modify source files.
  • Respect for .specify/memory/constitution.md principles and extension hooks when present.
  • Output a structured analysis report and a remediation plan (optional, available upon request).

Quick Start

Run the speckit-analyze command from the project root after task generation 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.md, plan.md, and tasks.md?

Cross-artifact consistency checks identify conflicts, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. They surface misalignments before implementation begins, improving overall project specification accuracy.

How do I analyze spec.md, plan.md, and tasks.md without modifying the files?

You can validate your project artifacts against constitution.md principles by running an analysis that respects extension hooks and consults .specify/memory/constitution.md. This validates your specifications against established principles to ensure alignment.

Can I generate a remediation plan after finding ambiguities in my spec documents?

You should run cross-artifact analysis after speckit-tasks has produced tasks.md. The analysis consults .specify/memory/constitution.md for principle validation and operates in read-only mode to output a structured analysis report.

What is the best way to surface conflicts between a project plan and its tasks?

Yes, cross-artifact analysis operates in strictly read-only mode. It reviews spec.md, plan.md, and tasks.md to output a structured analysis report without modifying any source files or altering your project state.

Does the cross-artifact analysis respect constitution.md principles and extension hooks?

Cross-artifact analysis identifies inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. This improves alignment before implementation by surfacing conflicts in a structured report.

When do I need to run cross-artifact consistency analysis on my specification files?

Cross-artifact analysis identifies inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. This improves alignment before implementation by surfacing conflicts in a structured report.