speckit-analyze

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

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/szaher/agentspec --skill speckit-analyze-szaher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/szaher/agentspec/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/szaher/agentspec --skill speckit-analyze-szaher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies inconsistencies, duplications, and gaps across your project's specification, plan, and task documents, ensuring a coherent and complete development roadmap before implementation.

Core Features & Use Cases

  • Cross-Artifact Analysis: Compares spec.md, plan.md, and tasks.md for alignment.
  • Inconsistency Detection: Flags conflicting requirements, terminology drift, and coverage gaps.
  • Use Case: After generating tasks for a new feature, run this Skill to verify that all requirements are covered by tasks and that no task contradicts the project's constitution.

Quick Start

Run the speckit analyze skill to check the consistency of your project artifacts.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my project specification and planning documents for consistency?

Cross-artifact consistency analysis compares spec.md, plan.md, and tasks.md to identify gaps, duplications, and conflicting requirements across your project artifacts. This ensures a coherent development roadmap before implementation begins.

What is cross-artifact consistency analysis for project specifications?

Cross-artifact consistency analysis is the process of comparing specification, planning, and task documents to detect terminology drift and coverage gaps. It verifies that all requirements are covered by tasks and align with the project constitution.

Do I need a specific directory structure to analyze project artifacts?

Yes, cross-artifact consistency analysis requires a .specify/ project structure with prerequisite scripts for context derivation. Without this directory structure and its required setup, the analysis cannot derive the necessary document context.

When should I run a consistency check on my specification and task documents?

You should run consistency analysis after generating tasks for a new feature, before implementation begins. This verifies that all specification requirements are covered by tasks and that no task contradicts the project constitution.

What's the best way to detect terminology drift between spec and task documents?

Performing cross-artifact consistency analysis flags terminology drift by comparing spec.md, plan.md, and tasks.md for alignment. It detects conflicting requirements and coverage gaps to ensure complete and coherent development planning.

Why does my task list have coverage gaps compared to my project specification?

Coverage gaps occur when task documents lack alignment with specification requirements. Running cross-artifact consistency analysis identifies these missing requirements by comparing spec.md, plan.md, and tasks.md against the project constitution.