speckit-analyze

Analyzes spec.md, plan.md, tasks.md inconsistencies, duplications, ambiguities and gaps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-analyze-leonardomoraisf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/leonardomoraisf/commonplace-pinboard-extension/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-analyze-leonardomoraisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Cross-artifact consistency checks across spec.md, plan.md, and tasks.md
  • Duplication and ambiguity detection across core artifacts
  • Gap identification and remediation planning to reduce rework

Quick Start

Run Speckit Analyze to generate a structured report of cross-artifact inconsistencies.

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 tasks artifacts before implementation?

To check for inconsistencies across spec.md, plan.md, and tasks.md, run a cross-artifact analysis to detect duplications, ambiguities, and underspecified items. This generates a structured report detailing coverage gaps and alignment issues to resolve before coding begins.

What is cross-artifact gap detection and when do I need it for spec planning?

Cross-artifact gap detection identifies underspecified items and coverage mismatches across specification, planning, and task artifacts. You need it after generating your tasks.md to ensure full alignment with your spec.md and plan.md before starting the implementation phase.

How do I identify duplications and ambiguities in spec, plan, and tasks files?

Identify duplications and ambiguities in spec, plan, and tasks files by running an artifact analysis that cross-references the three documents. It returns a structured report highlighting overlapping definitions and vague requirements to clarify before development.

Can I verify constitution alignment for my project artifacts without manual review?

You can verify constitution alignment automatically by running an artifact analysis that references your constitution.md file. The analysis checks your spec, plan, and tasks artifacts against defined constitutional rules and reports any compliance deviations.

What's the best way to ensure plan and tasks alignment before starting development?

The best way to ensure plan and tasks alignment is to execute a cross-artifact consistency check after completing your tasks.md. This detects coverage gaps and ambiguities between the plan and tasks, producing a remediation plan to reduce future rework.