speckit-analyze

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/luansilvadb/divi-app --skill speckit-analyze-luansilvadb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/luansilvadb/divi-app/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/luansilvadb/divi-app --skill speckit-analyze-luansilvadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-artifact quality and consistency are often broken during task generation, plan creation, and spec drafting, leading to hidden defects and rework. Speckit-analyze provides a structured review to surface these issues across spec.md, plan.md, and tasks.md with actionable insights.

Core Features & Use Cases

  • Cross-artifact consistency checks across spec.md, plan.md, and tasks.md.
  • Ambiguity and underspecification detection with actionable notes.
  • Constitution-alignment verification against project guidelines.

Quick Start

Run the speckit-analyze command after task generation to start the cross-artifact quality analysis.

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 after task generation, run a cross-artifact analysis. This process identifies inconsistencies, duplications, and ambiguities across the files to surface hidden defects and provide a remediation plan outline.

What is cross-artifact consistency analysis in a spec-kit project structure?

Cross-artifact consistency analysis in a spec-kit project structure reviews generated artifacts to detect underspecifications and misalignments. It verifies constitution-alignment against project guidelines and reports findings with a structured risk profile to prevent rework.

When do I need to analyze spec-kit artifacts for gaps and ambiguities?

You need to analyze spec-kit artifacts for gaps and ambiguities immediately after task generation. This timing ensures that any duplications or underspecifications introduced during plan creation and spec drafting are resolved before implementation begins.

Does speckit-analyze work with my existing .specify directory?

Yes, speckit-analyze works with your existing .specify directory by applying a structured review directly to the spec-kit project structure. It requires no additional dependencies to evaluate the cross-artifact quality of your generated files.

What is the best way to identify underspecifications across spec, plan, and tasks files?

The best way to identify underspecifications across spec, plan, and tasks files is to perform an automated cross-artifact review. This approach detects ambiguities and generates actionable notes alongside a concise report detailing a structured risk profile.

What limitations exist when detecting duplications across spec.md and plan.md?

When detecting duplications across spec.md and plan.md, the analysis is limited to identifying text-level inconsistencies and missing specifications. It provides a remediation plan outline but does not automatically rewrite or fix the artifact files for you.