speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and ambiguities.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/fly-eng/yzh --skill speckit-analyze-fly-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/fly-eng/yzh/tree/main/.kimi/skills/speckit-analyze
Command: npx skills add https://github.com/fly-eng/yzh --skill speckit-analyze-fly-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Core Features & Use Cases

  • Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts to prevent misinterpretation during implementation.
  • Surface actionable insights with a structured report and optional remediation plan to guide improvements.
  • Ensure alignment with the constitution to maintain project principles and quality gates.

Quick Start

Run the speckit-analyze command after speckit.tasks completes to surface inconsistencies across spec.md, plan.md, and tasks.md.

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 tasks.md for inconsistencies before implementation?

Cross-artifact consistency analysis identifies inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md before implementation begins.

When do I need cross-artifact quality validation for my specification?

Cross-artifact quality validation is needed after task generation completes to prevent misinterpretation during implementation and ensure alignment with project principles.

Does speckit-analyze modify files when validating specification and plan quality?

Speckit-analyze performs non-destructive quality analysis and does not modify any files, instead outputting a structured report with an optional remediation plan.

Can I validate project principles and quality gates during specification analysis?

Yes, the analysis consults the constitution at .specify/memory/constitution.md to validate principles and ensure alignment with established quality gates.

What is the best way to analyze tasks.md for duplications and ambiguities?

The best way to analyze tasks.md for duplications and ambiguities is running a cross-artifact consistency check that surfaces actionable insights with a structured remediation plan.

Why does specification analysis require tasks.md to be complete first?

Specification analysis requires a complete tasks.md because it performs cross-artifact validation across spec.md, plan.md, and tasks.md to identify underspecified items accurately.