speckit-analyze

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

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/byteflow-software/dellanosousa --skill speckit-analyze-byteflow-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/byteflow-software/dellanosousa/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/byteflow-software/dellanosousa --skill speckit-analyze-byteflow-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Core Features & Use Cases

  • Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md.
  • Output a structured analysis report and an optional remediation plan, while strictly reading data sources and honoring constitution constraints.
  • Applies only after speckit.tasks has produced a complete tasks.md in the feature directory.

Quick Start

Run the analysis to surface inconsistencies and ambiguities across spec.md, plan.md, and tasks.md after task generation.

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, plan, and tasks files?

To check for inconsistencies across spec, plan, and tasks files, you can run a cross-artifact analysis that identifies duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. It outputs a structured analysis report without modifying your files.

What is cross-artifact consistency analysis in software engineering?

Cross-artifact consistency analysis is the process of identifying mismatches, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. It surfaces quality issues by strictly reading data sources and enforcing constitution constraints to ensure requirements alignment.

When do I need to analyze tasks.md for requirements quality?

You need to analyze tasks.md for requirements quality after a complete tasks.md has been produced in your feature directory. Running the analysis at this stage surfaces inconsistencies and ambiguities across your spec, plan, and tasks before implementation begins.

Can I analyze spec and plan files without modifying my project directory?

Yes, you can analyze spec and plan files without modifying your project directory because the process is non-destructive. It strictly reads your data sources and outputs a structured analysis report while honoring constitution constraints, ensuring no file modifications occur.

What's the best way to find underspecified items in a feature spec?

The best way to find underspecified items in a feature spec is to perform a cross-artifact quality analysis across spec.md, plan.md, and tasks.md. This surfaces ambiguities and generates an optional remediation plan to address the gaps.

Does cross-artifact analysis generate a remediation plan for spec inconsistencies?

Yes, cross-artifact analysis generates an optional remediation plan for spec inconsistencies. Alongside the structured analysis report, it identifies duplications and underspecified items across spec.md, plan.md, and tasks.md to guide your corrections.