speckit-analyze

Detect gaps, duplications, and ambiguities across spec.md, plan.md, and tasks.md.

2|Updated Jan 29, 2026

Search Tags:#planning #consistency #specification #quality #traceability #speckit #gap-analysis

Ready to run

npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-analyze-pradeepmouli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-analyze
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-analyze-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies cross-artifact inconsistencies across spec.md, plan.md, and tasks.md to ensure alignment before implementation. This helps teams catch gaps, duplications, and ambiguities early to prevent rework.

Core Features & Use Cases

Cross-artifact analysis: compares spec, plan, and tasks to surface inconsistencies and misalignments across artifacts.
Gap and duplication detection: highlights missing mappings, duplicate entries, and traceability gaps.
Remediation guidance: suggests concrete improvements to bring artifacts into alignment before implementation.
Use Case: After generating tasks, run Speckit Analyze to ensure all requirements are covered and traceable.

Quick Start

Execute speckit-analyze after task generation to surface 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 check for inconsistencies across spec, plan, and task documents?▼

To check for inconsistencies across spec, plan, and task documents, analyze the artifacts to identify cross-artifact misalignments, gaps, and duplications before implementation begins.

What is cross-artifact gap analysis in software planning?▼

Cross-artifact gap analysis in software planning compares specifications, plans, and tasks to highlight missing mappings and traceability gaps, ensuring all requirements are fully covered and traceable.

When should I analyze tasks for consistency with my project specification?▼

You should analyze tasks for consistency with your project specification immediately after task generation, detecting ambiguities and duplications early to prevent rework before implementation.

How do I ensure traceability from requirements to tasks before coding?▼

To ensure traceability from requirements to tasks before coding, perform a cross-artifact analysis that detects missing mappings and enforces constitution-compliant checks across all planning documents.

Can I detect duplicate entries across spec.md, plan.md, and tasks.md?▼

Yes, you can detect duplicate entries across spec.md, plan.md, and tasks.md by running a cross-artifact analysis that highlights duplications and suggests concrete remediation improvements for alignment.

What are the limitations of automated spec and plan consistency checks?▼

Automated spec and plan consistency checks require distinct spec.md, plan.md, and tasks.md artifacts to function, meaning incomplete or unstructured planning documents will limit gap detection and traceability enforcement capabilities.