speckit-analyze

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

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-analyze-pieberrykinnie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/pieberrykinnie/hapa/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-analyze-pieberrykinnie

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, underspecification, 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 severity findings, metrics, and next-action recommendations. - Use Case: After running /speckit-tasks on a feature, run this analysis to confirm every requirement has task coverage and no constitution principle is violated before starting implementation. ## Quick Start Ask the agent to run a consistency analysis across the current feature's spec, plan, and tasks files and report any critical issues.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check consistency between spec, plan, and tasks files?

Run the analysis after tasks.md is generated. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and reports duplications, ambiguities, inconsistencies, and coverage gaps in a severity-ranked table.

What does the spec-kit analyze command detect?

It detects near-duplicate requirements, vague or unmeasurable wording, unresolved placeholders, constitution violations, requirements with zero task coverage, unmapped tasks, terminology drift, and conflicting requirements across the three artifacts.

Does the analysis modify my spec or tasks files?

No. The analysis is strictly read-only and never modifies files. It outputs a structured report and optionally offers remediation suggestions, which require explicit user approval before any follow-up editing commands run.

When should I run the analysis in the spec-kit workflow?

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. It requires a spec-kit project structure with a .specify directory and aborts if any required artifact is missing.

How are findings prioritized in the analysis report?

Findings are assigned CRITICAL, HIGH, MEDIUM, or LOW severity. Constitution MUST violations and uncovered blocking requirements are CRITICAL, while style issues are LOW. The report caps at 50 findings with an overflow summary.