speckit-analyze

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

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-analyze-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-analyze-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch inconsistencies, duplication, ambiguity, and missing coverage across specification artifacts before implementation starts, reducing rework and review churn.

Core Features & Use Cases

  • Cross-artifact analysis: Compares spec.md, plan.md, and tasks.md to find mismatched terminology, conflicting requirements, and incomplete task coverage.
  • Constitution compliance checks: Flags any violations against the project constitution so critical process rules are not missed.
  • Coverage reporting: Summarizes which requirements have task support and which items still need attention before execution.
  • Use Case: A product or engineering lead can run this Skill after task generation to validate that every important requirement is represented and that the implementation plan is internally consistent.

Quick Start

Ask the Skill to review the project’s spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps, then return a concise analysis report with prioritized recommendations.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my spec.md and tasks.md for inconsistencies before implementation?

To check spec.md and tasks.md for inconsistencies, you can cross-analyze the artifacts to find mismatched terminology, conflicting requirements, and incomplete task coverage before engineering begins.

What is cross-artifact analysis in specification planning?

Cross-artifact analysis compares spec.md, plan.md, and tasks.md to identify mismatched terminology, conflicting requirements, and incomplete task coverage across the specification and planning documents.

How do I verify requirement coverage and task mapping for my project?

You verify requirement coverage and task mapping by comparing the specification against the task list to ensure every important requirement is represented and has supporting implementation tasks.

Can I run a constitution compliance check on my project artifacts?

Yes, you can run a constitution compliance check against your project constitution to flag any violations and ensure critical process rules are not missed during pre-implementation validation.

Does this approach work for finding duplication and ambiguity in specifications?

Yes, analyzing specification and planning artifacts helps find duplication and ambiguity in your documentation, reducing rework and review churn before the implementation phase starts.

What is the best way to audit pre-implementation planning documents?

The best way to audit pre-implementation planning documents is to analyze spec.md, plan.md, and tasks.md together to produce a structured report with prioritized recommendations for gaps and inconsistencies.