speckit-analyze

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

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/kimen-dev/kimen --skill speckit-analyze-kimen-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/kimen-dev/kimen/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/kimen-dev/kimen --skill speckit-analyze-kimen-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves project drift by identifying inconsistencies, ambiguities, and coverage gaps between your specification, implementation plan, and task list.

Core Features & Use Cases

  • Cross-Artifact Validation: Automatically checks for alignment between spec.md, plan.md, and tasks.md.
  • Constitution Enforcement: Ensures all project work adheres to the defined project constitution and quality gates.
  • Use Case: After generating a task list for a new feature, run this skill to ensure every functional requirement is covered by a task and that no technical constraints are violated.

Quick Start

Run the speckit-analyze skill to perform a full consistency check across your current 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 validate consistency across spec.md, plan.md, and tasks.md?

To validate consistency across spec.md, plan.md, and tasks.md, run an automated cross-artifact analysis to check alignment, verify requirement coverage, and detect gaps between your specifications and task lists.

What is cross-artifact consistency analysis in software development?

Cross-artifact consistency analysis is an automated quality gate that identifies inconsistencies, ambiguities, and coverage gaps between your specification, implementation plan, and task list to prevent project drift and ensure strict requirement adherence.

When do I need to run specification validation for project management?

You need to run specification validation after generating a task list for a new feature to ensure every functional requirement is covered by a task and that no technical constraints are violated before implementation begins.

Can I enforce project constitution rules during task list generation?

Yes, you can enforce project constitution rules by running a non-destructive quality analysis that ensures all project work and generated tasks adhere to defined constraints and quality gates across your artifacts.

What's the best way to detect coverage gaps in technical specifications?

The best way to detect coverage gaps in technical specifications is to perform automated cross-artifact validation that targets software development workflows requiring strict adherence to project constitutions and functional requirement mapping.