skills.rest
alansmello
alansmelloCOMMUNITY
Explore all skills by this author →
𝕏@alansmelloGitHub

speckit-analyze

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

Updated Mar 18, 2026
Search Tags:#planning#consistency#spec-kit#analyze#gaps#artifact-quality
One-click install
npx skills add https://github.com/alansmello/Amani_ImportadosERP --skill speckit-analyze-alansmello
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/alansmello/Amani_ImportadosERP/tree/main/.cursor/skills/speckit-analyze
Command: npx skills add https://github.com/alansmello/Amani_ImportadosERP --skill speckit-analyze-alansmello

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Identifies inconsistencies, duplications, ambiguities, and underspecifications across the three core artifacts.
  • Validates alignment with the project constitution and highlights coverage gaps to guide remediation.
  • Generates a compact analysis report suitable for quick decision-making and subsequent task updates.

Quick Start

Run speckit-analyze from the project root after tasks.md is generated to produce a structured 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 spec.md, plan.md, and tasks.md for inconsistencies after task generation?▼

To check spec.md, plan.md, and tasks.md for inconsistencies after task generation, run a cross-artifact analysis from the project root to identify duplications, ambiguities, and coverage gaps. It produces a compact, token-efficient report enforcing constitution rules for quick remediation planning.

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

Cross-artifact consistency analysis in a spec-kit project is a non-destructive validation of alignment across spec.md, plan.md, and tasks.md. It identifies underspecifications and coverage gaps, validating outputs against the constitution rules to generate a deterministic report highlighting areas needing remediation.

Do I need a specific directory structure to analyze spec-kit artifacts?▼

Yes, cross-artifact analysis requires the standard .specify directory structure to validate spec-kit artifacts. Projects must follow this layout and have a generated tasks.md file so the analysis can accurately evaluate alignment, identify ambiguities, and output a deterministic consistency report.

How do I identify coverage gaps and duplications across planning artifacts?▼

To identify coverage gaps and duplications across planning artifacts, execute a cross-artifact quality analysis after tasks.md generation. It detects inconsistencies and ambiguities across spec.md, plan.md, and tasks.md, outputting a structured analysis report suitable for immediate decision-making and subsequent updates.

Does the analysis report modify the original spec-kit files?▼

No, cross-artifact analysis is strictly non-destructive and does not modify the original spec-kit files. It reads spec.md, plan.md, and tasks.md to produce a separate, compact analysis report highlighting duplications and coverage gaps ready for remediation planning.

Related Skills

Explore More Software Engineering Skills→
jineynejineyne

speckit-analyze

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

Community
Advanced
ins-encoins-enco

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps.

Official
Advanced
PieroSierraPieroSierra
128

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality.

Community
Advanced
dmae97dmae97
130

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality gaps.

Community
Advanced