speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality.

4|Updated May 16, 2025
One-click install
npx skills add https://github.com/AustinZ21/EggHatch-AI --skill speckit-analyze-austinz21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/AustinZ21/EggHatch-AI/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/AustinZ21/EggHatch-AI --skill speckit-analyze-austinz21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of implementing misaligned project requirements by identifying inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md files after task generation, preventing costly rework late in the development cycle.

Core Features & Use Cases

  • Cross-Artifact Consistency Checks: Validates alignment between project specifications, implementation plans, and task lists to catch conflicting requirements or missing coverage.
  • Constitution Alignment Validation: Ensures all project artifacts comply with the non-negotiable principles defined in your project constitution.
  • Coverage Gap Detection: Identifies requirements with no associated tasks and unmapped tasks to ensure full implementation coverage. Use Case: For a spec-kit software project, run this skill immediately after generating your tasks.md file to catch misalignments before your team starts writing code.

Quick Start

Invoke the speckit-analyze skill after completing your task generation step to receive a structured, severity-ranked report of all cross-artifact issues and coverage gaps.

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 pre-implementation, run a cross-artifact consistency analysis on your spec-kit project. This identifies duplications, ambiguities, and underspecified items to prevent costly rework late in the development cycle.

What is cross-artifact consistency analysis in spec-kit structured projects?

Cross-artifact consistency analysis in spec-kit structured projects validates alignment between specifications, implementation plans, and task lists. It checks for conflicting requirements, constitution conflicts, and missing coverage across core artifacts to ensure full implementation coverage.

How do I validate task coverage and constitution alignment after generating tasks.md?

You validate task coverage and constitution alignment by analyzing the generated tasks.md against your project constitution. This detects requirements with no associated tasks and unmapped tasks, ensuring all artifacts comply with non-negotiable principles.

Do I need a .specify directory to run a pre-implementation validation on my project?

Yes, you need a .specify directory to run pre-implementation validation. The analysis requires access to the project's .specify directory, core specification artifacts, and project constitution to generate a structured report with severity-ranked findings.

What is the best way to detect underspecified items and coverage gaps in spec-kit files?

The best way to detect underspecified items and coverage gaps in spec-kit files is to perform a non-destructive quality analysis across spec.md, plan.md, and tasks.md. This generates a structured report with severity-ranked findings and coverage metrics.

Why does my spec-kit project have unmapped tasks and conflicting requirements?

Your spec-kit project has unmapped tasks and conflicting requirements due to misaligned project artifacts. Running a post-task-generation validation identifies these duplications, ambiguities, and underspecified items across your files before implementation begins.