speckit-analyze

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

Updated May 31, 2026
One-click install
npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-analyze-piklar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Piklar/Rizza-60/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-analyze-piklar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves inconsistencies, ambiguities, and coverage gaps between specification, planning, and task artifacts, ensuring that project documentation remains aligned and actionable.

Core Features & Use Cases

  • Consistency Validation: Detects terminology drift and conflicting requirements across spec.md, plan.md, and tasks.md.
  • Coverage Analysis: Identifies requirements lacking associated tasks and tasks that do not map to defined success criteria.
  • Constitution Enforcement: Automatically flags violations of project-specific principles defined in the constitution.

Quick Start

Run the speckit-analyze command to perform a comprehensive 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 check cross-artifact consistency across spec.md, plan.md, and tasks.md?

To check cross-artifact consistency, run the speckit-analyze command to perform a non-destructive quality analysis that detects terminology drift, conflicting requirements, and coverage gaps across your project documentation.

What is documentation coverage analysis in a spec-kit project?

Documentation coverage analysis identifies requirements lacking associated tasks and tasks that do not map to defined success criteria, ensuring your spec.md, plan.md, and tasks.md artifacts remain aligned and actionable.

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

Yes, you need a valid spec-kit project structure with a .specify directory to execute the validation logic, as the analysis requires this environment to evaluate your documentation for duplication, ambiguity, and underspecification.

Can I enforce constitution alignment and flag principle violations in my project documentation?

You can enforce constitution alignment by running a consistency check that automatically flags violations of project-specific principles defined in your constitution across your specification, planning, and task artifacts.

What's the best way to find ambiguity and duplication across project planning and task artifacts?

The best way to find ambiguity and duplication is to perform a comprehensive consistency check that evaluates your project documentation for conflicting requirements, terminology drift, and underspecification across all artifacts.

Why does terminology drift occur between specification and planning documents?

Terminology drift occurs when evolving requirements introduce inconsistent language across documents, which cross-artifact consistency validation detects by comparing terminology usage across your spec.md, plan.md, and tasks.md files.