speckit-analyze

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

1|1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/erikalira/python-tts --skill speckit-analyze-erikalira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/erikalira/python-tts/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/erikalira/python-tts --skill speckit-analyze-erikalira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform a cross-artifact validation to surface inconsistencies, duplications, ambiguities, and gaps between spec.md, plan.md, and tasks.md to improve alignment before implementation.

Core Features & Use Cases

  • Cross-artifact consistency checks across spec.md, plan.md, and tasks.md.
  • Constitution-adherence validation against .specify/memory/constitution.md.
  • Use Case: Before coding, run speckit-analyze to identify missing mappings and conflicting requirements.

Quick Start

Run the analysis on your current spec, plan, and tasks to surface inconsistencies and gaps before implementation.

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 between spec, plan, and tasks files before coding?

Perform cross-artifact consistency checks to identify inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md. This validation ensures strict alignment between initial definitions, architectural plans, and execution tasks before implementation begins.

What is cross-artifact gap-analysis for project specs and tasks?

Cross-artifact gap-analysis identifies and surfaces inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md. It enforces strict alignment between initial definitions, architectural plans, and execution tasks, satisfying requirements for structured task coverage.

When do I need to validate constitution adherence in my project documentation?

Validate constitution adherence when projects enforce strict alignment rules defined in .specify/memory/constitution.md. This validation ensures spec.md, plan.md, and tasks.md comply with established constitutional constraints before implementation begins.

Can I use gap-analysis to find missing mappings between requirements and execution tasks?

Yes, gap-analysis finds missing mappings by performing cross-artifact validation across spec.md, plan.md, and tasks.md. It surfaces gaps and conflicting requirements between initial definitions and execution tasks to improve alignment before implementation.

Does cross-artifact validation work without a constitution.md file?

Constitution-adherence validation specifically requires .specify/memory/constitution.md to verify compliance. While consistency checks across spec.md, plan.md, and tasks.md may function independently, constitution validation depends on this file to enforce strict alignment rules.