speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and gaps in Speckit projects.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/GarethJB/workflow-plugin --skill speckit-analyze-garethjb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/GarethJB/workflow-plugin/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/GarethJB/workflow-plugin --skill speckit-analyze-garethjb

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill analyzes inconsistencies, duplications, ambiguities, and underspecifications across spec.md, plan.md, and tasks.md within Speckit projects, helping teams tighten contracts before implementation.

## Core Features & Use Cases

  • Detect cross-artifact mismatches and missing mappings between FRs, tasks, and plans.
  • Enforce constitution alignment and highlight gaps where no tasks cover a requirement.
  • Produce a compact, structured report that guides remediation and improvement.

### Quick Start Run /speckit.analyze after the tasks.md is 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 detect inconsistencies between spec, plan, and tasks files?

Cross-artifact analysis identifies inconsistencies, duplications, ambiguities, and underspecifications across spec.md, plan.md, and tasks.md by building semantic models and mapping tasks to requirements to surface missing coverage before implementation.

Why do I have uncovered requirements in my project tasks?

Uncovered requirements occur when no tasks map to specific functional requirements. Gap-analysis targets this by enforcing constitution alignment and highlighting exactly where task coverage is missing within your Speckit project artifacts.

When should I run cross-artifact gap analysis on my Speckit project?

Run cross-artifact gap analysis after tasks.md is generated to produce a structured report. This timing ensures spec.md, plan.md, and tasks.md exist so semantic models can be built to detect issues before implementation begins.

What is the best way to check traceability between functional requirements and tasks?

Checking traceability is done by mapping tasks to requirements across spec.md and tasks.md. This cross-artifact analysis detects missing mappings and produces a compact, structured report that guides remediation of coverage gaps.

Does Speckit gap analysis work without a constitution or artifact structure?

No, the analysis specifically targets projects following the Speckit constitution and artifact structure. It loads spec.md, plan.md, and tasks.md artifacts to build semantic models, requiring this standardized structure to detect issues accurately.

What types of specification issues can cross-artifact analysis find?

Cross-artifact analysis finds inconsistencies, duplications, ambiguities, and underspecifications across spec.md, plan.md, and tasks.md. It maps tasks to functional requirements and detects mismatches to ensure full coverage and traceability before implementation.