speckit-analyze

Analyze spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md to detect duplications, ambiguities, underspecified requirements, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects terminology drift, conflicting requirements, and data entities referenced in one artifact but missing from others. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero task coverage and unmapped tasks. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW findings, coverage metrics, and next-action recommendations. - Use Case: After running /speckit-tasks, invoke this Skill to verify that all requirements have task coverage and no constitution principles are violated before starting /speckit-implement. ## Quick Start Run the speckit-analyze skill 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 spec consistency before implementation in spec-kit?▼

Run the speckit-analyze command after /speckit-tasks completes. It loads spec.md, plan.md, and tasks.md, then reports duplications, ambiguities, coverage gaps, and constitution violations in a severity-ranked Markdown report without modifying any files.

What does speckit-analyze detect in specification files?▼

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

Does speckit-analyze modify my spec or tasks files?▼

No, the analysis is strictly read-only. It outputs a structured report and offers an optional remediation plan, but edits are only applied after explicit user approval through separate follow-up commands.

When should I run speckit-analyze in the 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, instructing you to run the prerequisite command first.

Why does speckit-analyze report constitution conflicts as critical?▼

The project constitution at .specify/memory/constitution.md is treated as non-negotiable. Any requirement or plan element conflicting with a MUST principle is automatically assigned CRITICAL severity and requires adjusting the spec, plan, or tasks.