speckit-analyze

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

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/kerolos-saaid/refranario --skill speckit-analyze-kerolos-saaid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/kerolos-saaid/refranario/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/kerolos-saaid/refranario --skill speckit-analyze-kerolos-saaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and resolve inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md after task generation.

Core Features & Use Cases

  • Surface cross-artifact issues across documentation artifacts to ensure alignment and completeness.
  • Provide a structured findings report with severity, mappings, and suggested remediations.
  • Applicable to projects using the speckit workflow with a .specify/ structure to improve pre-implementation governance.

Quick Start

Run the analysis to generate a findings report for the current 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 for inconsistencies across spec.md, plan.md, and tasks.md?

To check for inconsistencies across spec.md, plan.md, and tasks.md, you can run a cross-artifact quality analysis to identify duplications, ambiguities, and underspecified items. This generates a structured findings report detailing severity and suggested remediations.

What is cross-artifact quality analysis for spec files?

Cross-artifact quality analysis for spec files is the process of validating conformance to the constitution and mapping coverage between requirements and tasks. It highlights critical gaps that block baseline functionality after task generation.

How do I validate task coverage against requirements in a .specify/ structure?

You validate task coverage against requirements in a .specify/ structure by analyzing the generated tasks.md alongside spec.md and plan.md. This maps coverage between requirements and tasks to surface underspecified items and critical gaps.

Can I use this analysis for projects without a .specify/ directory structure?

No, this analysis targets speckit-managed projects specifically requiring a .specify/ directory structure. It relies on this environment to validate conformance and map coverage between the spec.md, plan.md, and tasks.md artifacts.

Why does my spec plan have ambiguities and underspecified items after task generation?

Spec plans develop ambiguities and underspecified items after task generation due to misalignment across documentation artifacts. Running a cross-artifact analysis identifies these issues and provides suggested remediations to improve pre-implementation governance.

What is the best way to resolve duplications in speckit documentation artifacts?

The best way to resolve duplications in speckit documentation artifacts is to run a cross-artifact analysis that produces a structured findings report. This report maps the duplications and provides suggested remediations to ensure alignment and completeness.