speckit-analyze

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

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dantasgut/clayflow --skill speckit-analyze-dantasgut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/dantasgut/clayflow/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/dantasgut/clayflow --skill speckit-analyze-dantasgut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and ensure quality across artifacts (spec.md, plan.md, and tasks.md) after task generation by performing a non-destructive cross-artifact consistency and quality analysis.

Core Features & Use Cases

  • Identify inconsistencies, duplications, ambiguities, and underspecified items across spec, plan, and tasks.
  • Produce a structured analysis report and optional remediation plan to guide improvements.
  • Operate in a strictly read-only mode, relying on the constitution and extension hooks to drive checks.

Quick Start

After you have generated tasks with /speckit-tasks, run /speckit-analyze to produce a structured analysis report.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for inconsistencies across spec.md, plan.md, and tasks.md?

To check for cross-artifact inconsistencies, you can run a consistency analysis that reads your spec, plan, and tasks files to identify duplications, ambiguities, and underspecified items in a structured report.

What is cross-artifact consistency analysis in spec-kit projects?

Cross-artifact consistency analysis is a read-only validation process that detects quality issues across spec.md, plan.md, and tasks.md by checking them against project principles in your constitution.md file.

How do I validate generated tasks against my spec-kit constitution?

You validate generated tasks by running a non-destructive analysis that reads .specify/memory/constitution.md for principle validation and uses .specify/extensions.yml to detect executable extension hooks, ensuring deterministic results.

Can I use cross-artifact analysis on a spec-kit project without a .specify directory?

No, cross-artifact analysis requires a spec-kit project with a .specify directory because it relies on reading .specify/memory/constitution.md and .specify/extensions.yml to drive quality checks and ensure accurate results.

Does the spec-kit analysis tool modify my spec, plan, or tasks files?

No, the spec-kit analysis tool operates in a strictly read-only mode to perform cross-artifact consistency checks, producing a structured analysis report and optional remediation plan without modifying your original files.

What is the best way to plan remediation for quality issues in spec-kit artifacts?

The best way to plan remediation is to generate a structured analysis report that identifies inconsistencies across spec.md, plan.md, and tasks.md, which then guides your improvements through an optional remediation plan.