speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-artifact inconsistencies, ambiguities, and coverage gaps across spec.md, plan.md, and tasks.md before implementation.

Core Features & Use Cases

  • Detects duplication, ambiguity, and underspecification across core artifacts.
  • Validate alignment with constitution rules and extension hooks.
  • Generate a compact, actionable analysis report with remediation suggestions.

Quick Start

Run a targeted analysis on the current feature folder to identify issues and mapping across artifacts.

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.md, plan.md, and tasks.md for inconsistencies before implementation?

Analyze your spec.md, plan.md, and tasks.md files to identify cross-artifact inconsistencies, duplications, ambiguities, and coverage gaps. Run a targeted analysis on your feature folder to output a compact, deterministic report highlighting issues.

What is the best way to validate constitution rules and extension hooks across project artifacts?

Validate alignment with constitution rules and extension hooks by running a consistency analysis across your core artifacts. This generates an actionable report detailing any detected duplications or underspecification issues.

How do I find coverage gaps and ambiguities in my project spec and task definitions?

Detect coverage gaps and ambiguities in your project spec and task definitions by analyzing the artifacts for underspecification. The analysis outputs remediation suggestions to resolve the identified alignment issues.

Does spec and plan analysis work without additional dependencies?

Yes, consistency and constitution validation across spec.md, plan.md, and tasks.md works without additional dependencies. It directly analyzes the feature folder artifacts to produce a deterministic issues report.

What limitations exist when validating alignment across spec.md, plan.md, and tasks.md?

Alignment validation is limited to detecting duplications, ambiguities, and coverage gaps across spec.md, plan.md, and tasks.md. It outputs a compact report with suggested remediation but does not modify the artifacts directly.