speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and quality issues.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Yangeok/i-cherri --skill speckit-analyze-yangeok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Yangeok/i-cherri/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/Yangeok/i-cherri --skill speckit-analyze-yangeok

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures project artifacts, like spec.md, plan.md, and tasks.md, are consistent and meet quality standards, minimizing errors before implementation.

Core Features & Use Cases

  • Cross-Artifact Analysis: Checks for inconsistencies, duplications, ambiguities, and underspecifications across project documents.
  • Compatibility: Designed for spec-kit projects with .specify/ directory.
  • Use Case: After generating tasks with /speckit-tasks, this Skill identifies potential issues that need attention before proceeding with implementation.

Quick Start

Run /speckit-analyze to perform an analysis on your project's 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.md, plan.md, and tasks.md files?

To check consistency across spec.md, plan.md, and tasks.md files, you can run an analysis to identify inconsistencies, duplications, and ambiguities. This validates your project artifacts to ensure quality and minimize errors before implementation.

What is cross-artifact analysis in a spec-kit project structure?

Cross-artifact analysis in a spec-kit project structure is the process of scanning project documents for inconsistencies, duplications, ambiguities, and underspecifications. It operates within the .specify/ directory to maintain development integrity.

Do I need to complete /speckit-tasks before analyzing project artifacts?

Yes, you need to complete the /speckit-tasks command before analyzing project artifacts. The analysis requires the generated tasks.md file to perform cross-artifact consistency checking and identify potential issues accurately.

How do I find underspecifications in my project documentation?

To find underspecifications in your project documentation, run an automated analysis on your spec-kit artifacts. This process scans spec.md, plan.md, and tasks.md files to detect ambiguities and missing specifications before you proceed with implementation.

Can I use this artifact analysis without a .specify/ directory?

No, you cannot use this artifact analysis without a .specify/ directory. The tool is specifically designed to operate within the spec-kit project structure, requiring this directory to validate spec.md, plan.md, and tasks.md files.

Why does my spec-kit project have duplications across plan and tasks files?

Duplications across plan and tasks files occur when implementation details are redundantly specified. Running a cross-artifact analysis identifies these duplications, alongside inconsistencies and ambiguities, ensuring your documentation meets quality standards.