speckit-analyze

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

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-analyze-xyphyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/xyphyx/internal-project-template/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-analyze-xyphyx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md before implementation to ensure a coherent project scope and executable plan.

Core Features & Use Cases

  • Cross-artifact analysis: checks consistency and quality across spec.md, plan.md, and tasks.md.
  • Constitution alignment: detects deviations from project constitution and mandated sections.
  • Coverage mapping: maps requirements to tasks and highlights gaps.

Quick Start

Run speckit-analyze after tasks.md is generated to scan spec.md, plan.md, and tasks.md for inconsistencies.

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 inconsistencies before implementation?

To check spec.md, plan.md, and tasks.md for inconsistencies, run a cross-artifact analysis that identifies duplications, ambiguities, and underspecified items to ensure a coherent project scope. It produces a compact report with prioritized findings and remediation steps.

What is cross-artifact analysis in specification-driven development?

Cross-artifact analysis in specification-driven development is the process of scanning spec.md, plan.md, and tasks.md to identify coverage gaps and ensure alignment with the project constitution. It validates that requirements map correctly to planned tasks.

When should I analyze my project specification and task plan for coverage gaps?

You should analyze your project specification and task plan for coverage gaps immediately after tasks.md is generated. Running this check before implementation ensures your executable plan remains coherent and properly aligned with your project scope.

How do I map requirements to tasks and detect constitution deviations?

To map requirements to tasks and detect constitution deviations, use an analysis tool that checks your specification artifacts against mandated sections. This highlights coverage gaps, producing a compact report with recommended remediation steps.

Does spec-kit analysis work without a project constitution file?

Spec-kit analysis focuses on constitution alignment and detecting deviations from mandated sections. Without a project constitution, the analysis lacks the baseline needed to effectively evaluate scope coherence and identify specification deviations.