speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents implementation churn by finding inconsistencies, duplications, ambiguities, and missing coverage across your spec, plan, and tasks artifacts before work begins.

Core Features & Use Cases

  • Cross-artifact consistency analysis: Compares spec.md, plan.md, and tasks.md for requirement/task alignment and terminology drift.
  • Quality and completeness checks: Flags unclear success criteria, placeholders, underspecified items, and constitution violations.
  • Coverage and dependency mapping: Reports unmapped tasks and requirements that have no task coverage to support reliable execution.

Quick Start

Run /.claude/skills/speckit-analyze after /speckit.tasks has generated a complete tasks.md.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check task coverage and requirement alignment before implementation?

Cross-artifact consistency analysis compares your spec, plan, and tasks files to detect requirement coverage gaps, duplication, and ambiguities. It validates that generated tasks align with functional requirements and success criteria before coding begins.

How do I detect inconsistencies across spec, plan, and tasks documents?

Cross-artifact consistency analysis compares your spec, plan, and tasks files to detect terminology drift, unmapped tasks, and underspecified items. It automatically surfaces duplications and misalignments across your project artifacts.

What's the best way to validate MUST and SHOULD requirements from a project constitution?

Constitution validation loads your project's MUST and SHOULD constraints and checks your tasks and specs for violations. This read-only auditing process produces a structured analysis report without editing your existing files.

Do I need a complete tasks.md to run consistency analysis on my project specs?

Yes, cross-artifact consistency analysis applies after your tasks generation step has produced a complete tasks.md. Running it earlier means the tool cannot accurately map requirement coverage or flag unmapped tasks.

Can I audit spec and task alignment without modifying my project files?

Yes, read-only auditing loads your spec.md, plan.md, and tasks.md to perform quality and completeness checks. It flags unclear success criteria and placeholders while producing a structured report without editing any files.

Why does my implementation churn due to unmapped tasks and requirement gaps?

Implementation churn happens when tasks lack coverage for functional requirements or contain ambiguities. Cross-artifact consistency analysis identifies these gaps and dependency mapping issues before development work begins.