speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies, gaps, and constitution violations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and uncovered tasks that cause costly rework. This Skill performs a read-only cross-artifact consistency analysis so teams catch these issues early. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects duplications, ambiguities, underspecified requirements, and terminology drift across spec.md, plan.md, and tasks.md. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting coverage percentage and unmapped tasks. - Constitution Enforcement: Validates artifacts against the project constitution, flagging MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit.tasks, invoke this Skill to receive a structured severity-ranked report with remediation suggestions before starting /speckit.implement. ## Quick Start Run the speckit-analyze command to check my spec, plan, and tasks files for inconsistencies and coverage gaps 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 my spec and tasks for inconsistencies before implementation?

Run the speckit-analyze command after generating tasks.md. It loads spec.md, plan.md, and tasks.md, then produces a structured report of duplications, ambiguities, coverage gaps, and constitution violations ranked by severity.

What does the spec-kit analyze command detect?

It detects near-duplicate requirements, vague adjectives lacking measurable criteria, unresolved placeholders, requirements with zero task coverage, terminology drift, conflicting requirements, and violations of constitution MUST principles.

Does speckit-analyze modify my specification files?

No, the analysis is strictly read-only. It outputs a Markdown report with findings and recommendations, and only offers optional remediation suggestions that require explicit user approval before any edits.

When should I run the analyze step in a spec-kit workflow?

Run it after /speckit.tasks has produced a complete tasks.md and before /speckit.implement. It aborts with an error if required artifacts are missing, directing you to the prerequisite command.

Why does the analysis report CRITICAL issues for constitution conflicts?

The project constitution in .specify/memory/constitution.md is treated as non-negotiable. Any requirement or plan element conflicting with a MUST principle is automatically classified as CRITICAL and must be resolved in the artifacts, not the constitution.