speckit-analyze

Detect inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apply-the/canon --skill speckit-analyze-apply-the
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/apply-the/canon --skill speckit-analyze-apply-the

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies inconsistencies, duplications, ambiguities, and underspecified items across the core artifacts (spec.md, plan.md, and tasks.md) after task generation, helping teams maintain a coherent specification-to-workflow alignment.

Core Features & Use Cases

  • Cross-artifact consistency checks: validate that functional requirements, user stories, and tasks align across spec.md, plan.md, and tasks.md.
  • Duplication and ambiguity detection: surface near-duplicate requirements and vague phrasing with measurable criteria.
  • Constitution-aware validation: ensure alignment with project principles and memory constitution, surfacing conflicts for remediation.

Quick Start

Run the speckit.analyze command after the speckit.tasks step to generate a report of 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 detect inconsistencies across spec, plan, and tasks files?

You can spot inconsistencies across spec, plan, and tasks files by running an automated analysis after task generation to validate alignment, identify duplications, and surface ambiguities across spec.md, plan.md, and tasks.md.

Why does my generated tasks.md have duplicate requirements and vague phrasing?

Duplicate requirements and vague phrasing in tasks.md often stem from misalignment between spec.md and plan.md. Analyzing these artifacts surfaces near-duplicates and ambiguous items lacking measurable acceptance criteria.

When should I run a cross-artifact consistency check in a spec-kit workflow?

Run a cross-artifact consistency check in a spec-kit workflow immediately after tasks.md is generated. This validates that functional requirements, user stories, and tasks align before development begins.

Can I validate generated tasks against a project constitution?

Yes, you can validate generated tasks against a project constitution. The analysis references the constitution to ensure task alignment with project principles and surfaces any conflicts for remediation.

Does spec analysis modify the original spec.md and plan.md files?

Spec analysis does not modify the original spec.md and plan.md files. The process enforces a read-only constraint on the artifacts and outputs a separate structured analysis report detailing inconsistencies.