speckit-analyze

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

1.0k|514|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill speckit-analyze-unipds-engenharia-de-ia-aplicada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada/tree/main/lives/2026-05-27/001-pos-live/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill speckit-analyze-unipds-engenharia-de-ia-aplicada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews spec.md, plan.md, and tasks.md together to find inconsistencies, duplicates, ambiguities, missing coverage, and constitution conflicts before implementation begins.

Core Features & Use Cases

  • Cross-artifact consistency analysis: Compares requirements, architecture choices, and task lists to spot misalignment early.
  • Coverage gap detection: Identifies requirements and success criteria that have no task coverage, plus tasks that do not map back to a requirement.
  • Quality review for planning artifacts: Highlights duplication, vague wording, underspecified edge cases, and ordering problems in delivery plans.
  • Use case: A team has completed spec generation and task breakdown, and uses this Skill to validate the plan before starting implementation.

Quick Start

Ask the speckit-analyze skill to review spec.md, plan.md, and tasks.md for inconsistencies, coverage gaps, and constitution conflicts 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 spec and plan documents for inconsistencies before implementation?▼

To check spec and plan documents for inconsistencies, you analyze spec.md, plan.md, and tasks.md together to find misalignment, duplicates, ambiguities, and constitution conflicts before development begins.

What is cross-artifact consistency analysis in spec-driven development?▼

Cross-artifact consistency analysis compares requirements, architecture choices, and task lists across spec.md, plan.md, and tasks.md to spot misalignment early in the planning phase before code is written.

How do I find missing task coverage for requirements in a project plan?▼

To find missing task coverage, you map tasks back to requirements and success criteria, identifying which requirements have no task coverage and which tasks do not map back to a requirement.

How do I review planning artifacts for vague wording and duplication?▼

Reviewing planning artifacts involves highlighting duplication, vague wording, underspecified edge cases, and ordering problems in delivery plans to ensure quality before implementation starts.

When do I need to run a spec review on my planning artifacts?▼

You need a spec review when your team has completed spec generation and task breakdown and wants to validate the plan, check requirement mapping, and assess task coverage before starting implementation.

Does spec-driven quality validation work without a constitution alignment check?▼

Spec-driven quality validation requires a constitution alignment check to find conflicts alongside requirement mapping and task coverage assessment for a complete and actionable review output.