speckit-analyze

Analyze specification, planning, and task artifacts for consistency and gaps.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/Steve-Smith-CODE/yachakuqwasi --skill speckit-analyze-steve-smith-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Steve-Smith-CODE/yachakuqwasi/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/Steve-Smith-CODE/yachakuqwasi --skill speckit-analyze-steve-smith-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves inconsistencies, ambiguities, and gaps between specification, planning, and task documentation in Spec-Driven Development projects, preventing implementation errors before they occur.

Core Features & Use Cases

  • Cross-Artifact Validation: Automatically checks for alignment between spec.md, plan.md, and tasks.md.
  • Constitution Enforcement: Validates project requirements against the mandatory project constitution.
  • Use Case: After generating a feature plan, use this Skill to identify if any tasks are missing or if the proposed implementation contradicts the project's architectural principles.

Quick Start

Run the speckit-analyze skill to validate the consistency of the current feature specification and task list.

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 between spec, plan, and task documentation?

Cross-artifact validation checks alignment between specification, planning, and task documentation by evaluating spec.md, plan.md, and tasks.md to identify coverage gaps, ambiguities, and implementation contradictions before development begins.

What is spec-driven development consistency validation?

Spec-driven development consistency validation performs non-destructive analysis across specification, planning, and task artifacts to detect coverage gaps, ambiguities, and architectural misalignment, preventing implementation errors before they occur.

Do I need a .specify directory to validate spec-kit documentation?

Yes, executing spec-driven validation logic requires a .specify directory and the standard spec-kit file structure to be present in your project environment to run consistency and quality analysis.

When should I run consistency analysis on my feature specifications?

Run consistency analysis after generating a feature plan to identify missing tasks or verify that the proposed implementation does not contradict the project's mandatory architectural constitution.

How does constitution enforcement work in spec-driven development?

Constitution enforcement validates project requirements by checking specification and planning artifacts against the mandatory project constitution, ensuring all proposed tasks align with established architectural principles.

Can this analysis detect missing tasks in a feature plan?

Yes, the analysis detects missing tasks by evaluating alignment across specification, planning, and task artifacts to identify coverage gaps where planned tasks fail to fully implement the defined feature requirements.