speckit-analyze

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

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/ev3rlit/magam --skill speckit-analyze-ev3rlit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/ev3rlit/magam/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/ev3rlit/magam --skill speckit-analyze-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md to ensure alignment before implementation.

Core Features & Use Cases

  • Duplication detection across artifacts and risk flags for ambiguous or underspecified requirements.
  • Coverage mapping to show how tasks map to requirements or stories and highlight gaps.
  • Structured report with remediation recommendations and constitution alignment checks.

Quick Start

Run the speckit-analyze after tasks.md is generated to review artifacts and report issues 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 find gaps across spec, plan, and tasks files before implementation?

To find gaps across spec, plan, and tasks files, you need an analysis process that maps tasks to requirements and highlights missing coverage. This Skill identifies inconsistencies, duplications, and underspecified items across spec.md, plan.md, and tasks.md to ensure alignment before implementation.

What is the best way to check for inconsistencies between specs and tasks?

The best way to check for inconsistencies between specs and tasks is to perform coverage mapping and duplication detection across your artifacts. This analysis reviews spec.md, plan.md, and tasks.md to flag ambiguous requirements and produce a structured report with remediation recommendations.

When do I need to analyze spec files for duplications and ambiguities?

You need to analyze spec files for duplications and ambiguities immediately after task generation and before starting implementation. Running this analysis ensures comprehensive coverage and verifies that spec.md, plan.md, and tasks.md are fully aligned without underspecified items.

How do I map tasks to requirements to highlight missing coverage?

To map tasks to requirements and highlight missing coverage, run an analysis across your generated artifacts. This Skill produces coverage mapping that shows how tasks.md maps to spec.md requirements, identifying gaps and producing a structured report with remediation recommendations.

Can I get a structured report for spec and plan remediations before coding?

Yes, you can get a structured report for spec and plan remediations before coding. The analysis produces a report highlighting findings, risks, and remediations, including constitution alignment checks to ensure your spec.md, plan.md, and tasks.md are ready for implementation.