speckit-analyze

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

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/a2mus/smart-da3m --skill speckit-analyze-a2mus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/a2mus/smart-da3m/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/a2mus/smart-da3m --skill speckit-analyze-a2mus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify cross-artifact inconsistencies across spec.md, plan.md, and tasks.md. Use after task generation to identify gaps, duplications, and inconsistencies before implementation.

Core Features & Use Cases

  • Cross-artifact consistency checks across spec, plan, and tasks.
  • Identify duplications and ambiguities in artifacts.
  • Output a structured analysis report to guide remediation before implementation.

Quick Start

Run the speckit-analyze analysis on your project to generate a report.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
What is cross-artifact consistency analysis for spec, plan, and tasks files?

Cross-artifact consistency analysis identifies gaps, duplications, and inconsistencies across spec.md, plan.md, and tasks.md. It validates alignment before implementation to improve accuracy and outputs a structured report to guide remediation.

How do I check my spec.md and plan.md for inconsistencies before implementation?

To check for inconsistencies, run an analysis on your project artifacts after task generation. The analysis enforces a read-only principle during evaluation and outputs a structured report highlighting misalignments across your specification and planning documents.

Does cross-artifact analysis work with the .specify/ structure and task-generation workflows?

Yes, cross-artifact analysis is designed for projects following the .specify/ structure and task-generation workflows. You can use it to validate alignment between your generated tasks and original specifications before starting the implementation phase.

When should I run a cross-artifact analysis on my project documentation?

You should run cross-artifact analysis after task generation and before implementation. It identifies gaps and ambiguities in your artifacts at this stage, ensuring your implementation phase begins with accurate and aligned specification documents.

Can this analysis modify my spec.md and tasks.md files during the consistency check?

No, the analysis cannot modify your files because it enforces a strict read-only principle during evaluation. It only generates a structured analysis report detailing the inconsistencies and gaps, leaving your original artifacts untouched for manual remediation.

What is the best way to find duplications and ambiguities across specification artifacts?

The best way to find duplications and ambiguities is to run a cross-artifact consistency check across your spec, plan, and tasks files. This process evaluates the documents together and outputs a structured report to guide your remediation efforts.