speckit-analyze

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-analyze-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/speckit-analyze
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-analyze-wu-mao-chia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain duplications, ambiguities, coverage gaps, and contradictions 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 Analysis: Detects duplications, ambiguities, underspecification, inconsistencies, and coverage gaps across spec.md, plan.md, and tasks.md. - Constitution Enforcement: Validates artifacts against the project constitution (.specify/memory/constitution.md), flagging MUST-principle violations as CRITICAL. - Structured Report: Produces a severity-ranked findings table, requirement-to-task coverage summary, and metrics (coverage %, ambiguity count, critical issue count) with next-action recommendations. - Use Case: After running /speckit-tasks, invoke this Skill to verify every functional requirement has at least one task and no conflicting technology choices exist before running /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 spec.md and tasks.md for inconsistencies before implementation?▼

Run the speckit-analyze command after tasks.md has been generated. It loads spec.md, plan.md, and tasks.md, maps requirements to tasks, and outputs a severity-ranked findings report with coverage metrics and recommended next actions.

What does spec-kit analyze detect in specification artifacts?▼

It detects near-duplicate requirements, vague or unmeasurable wording, unresolved placeholders, underspecified requirements, terminology drift, conflicting requirements, tasks with no mapped requirement, and requirements with zero task coverage.

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

No, the analysis is strictly read-only. It outputs a structured Markdown report and only offers an optional remediation plan, which requires explicit user approval before any follow-up editing commands are invoked.

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 spec.md, plan.md, or tasks.md is missing, directing you to the prerequisite command.

How are constitution violations handled during analysis?▼

Conflicts with MUST principles in .specify/memory/constitution.md are automatically classified as CRITICAL findings. The constitution is treated as non-negotiable, so the spec, plan, or tasks must be adjusted rather than the principle.