speckit-analyze

Analyzes spec, plan, and tasks for duplication, ambiguity, and gaps in spec-kit projects.

Updated May 29, 2026

Search Tags:#code review #project analysis #consistency check #quality analysis #spec-kit

Ready to run

npx skills add https://github.com/juanca202/exercise-mobile --skill speckit-analyze-juanca202

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/juanca202/exercise-mobile/tree/main/.cursor/skills/speckit-analyze
Command: npx skills add https://github.com/juanca202/exercise-mobile --skill speckit-analyze-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill performs a thorough consistency and quality analysis of the core artifacts in a spec-kit project after task generation, identifying potential issues before implementation.

Core Features & Use Cases

Cross-Artifact Analysis: Consistency checks across spec.md, plan.md, and tasks.md.
Non-Destructive: Ensures no changes are made to the source files.
Detailed Reporting: Provides a structured report on identified issues and recommendations.

Quick Start

Run the analyze skill after task generation to ensure consistency and quality in 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 consistency across spec, plan, and tasks files?▼

You can check consistency across spec, plan, and tasks files by running a post-task generation analysis. This process evaluates the documents for duplication, ambiguity, underspecification, and coverage gaps, providing a detailed report without modifying the source files.

What does constitution alignment mean in project analysis?▼

Constitution alignment in project analysis verifies that your generated tasks and plans adhere to the foundational project constraints. This consistency check ensures the core artifacts remain consistent with the established constitution before implementation begins.

How do I detect coverage gaps in a spec-kit project?▼

To detect coverage gaps in a spec-kit project, you perform cross-artifact analysis between spec.md, plan.md, and tasks.md. This quality analysis identifies missing requirements and ensures all specifications are fully covered by the generated tasks.

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

Yes, you need a spec-kit project structure containing a .specify/ directory and specific artifacts to analyze. The consistency and quality analysis also requires the .specify/extensions.yml file to configure additional hooks for checking duplication and coverage gaps.

Can I run a consistency check without modifying my markdown files?▼

Yes, you can run a non-destructive consistency check that analyzes your spec, plan, and tasks without modifying the source files. It performs read-only cross-artifact checks and outputs a detailed report of identified issues and recommendations.

When should I run a quality analysis on my project artifacts?▼

You should run a quality analysis on your project artifacts post-task generation, right before implementation begins. This timing allows you to identify and resolve consistency issues, ambiguity, and underspecification early in the development lifecycle.