skills.rest
auravibes-apps
auravibes-appsOFFICIAL
Explore all skills by this author →
GitHub

speckit-analyze

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

Updated Aug 23, 2026
Search Tags:#consistency#specification#analysis#constitution#tasks#plan
One-click install
npx skills add https://github.com/auravibes-apps/auravibes --skill speckit-analyze-auravibes-apps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/auravibes-apps/auravibes/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/auravibes-apps/auravibes --skill speckit-analyze-auravibes-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It non-destructively analyzes spec.md, plan.md, and tasks.md after task generation to surface inconsistencies, duplications, ambiguities, and underspecified items, enabling targeted refinements across artifacts.

Core Features & Use Cases

  • Cross-checks consistency and alignment across the three core artifacts (spec.md, plan.md, tasks.md).
  • Detects missing mappings, conflicting requirements, and ambiguous terminology to improve traceability.
  • Generates a compact analysis report with actionable remediation guidance and traceability mappings.

Quick Start

Run /speckit.analyze from the repo root after tasks.md has been generated to produce a structured 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 spec.md, plan.md, and tasks.md for consistency after task generation?▼

To check spec.md, plan.md, and tasks.md for consistency, run /speckit.analyze from the repository root. It identifies inconsistencies, duplications, ambiguities, and underspecified items across the artifacts.

What is the best way to find missing mappings and conflicting requirements across project artifacts?▼

Finding missing mappings and conflicting requirements is handled by cross-checking spec.md, plan.md, and tasks.md. This analysis detects conflicting requirements and ambiguous terminology to improve overall traceability.

Does the consistency analysis modify the original specification and plan files?▼

No, the consistency analysis is non-destructive. It surfaces inconsistencies and underspecified items across your artifacts, generating a compact analysis report with remediation guidance instead of altering the files.

Can I use this analysis on a project that does not follow the spec-kit structure?▼

No, you cannot use this on projects outside the spec-kit structure. The analysis is scoped to projects relying on the spec-kit structure and validates principles using the constitution.

How do I get actionable remediation guidance for ambiguous terminology in my tasks?▼

To get actionable remediation guidance for ambiguous terminology, run the analysis after task generation. It outputs a compact analysis report with optional remediation steps and traceability mappings.

When should I run a specification and tasks consistency analysis in my workflow?▼

You should run the specification and tasks consistency analysis after tasks.md has been generated. This timing ensures all three core artifacts exist and can be cross-checked for alignment and duplications.

Related Skills

Explore More Software Engineering Skills→
PieroSierraPieroSierra
128

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality.

Community
Advanced
auleewilliamsauleewilliams

speckit-analyze

Detect inconsistencies across spec.md, plan.md, and tasks.md files.

Community
Advanced
PiklarPiklar

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality.

Community
Intermediate
pradeepmoulipradeepmouli
2

speckit-analyze

Detect gaps, duplications, and ambiguities across spec.md, plan.md, and tasks.md.

Community
Advanced