speckit-analyze

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

44|10|Updated Mar 28, 2024
One-click install
npx skills add https://github.com/sensein/senselab --skill speckit-analyze-sensein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/sensein/senselab/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/sensein/senselab --skill speckit-analyze-sensein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, duplicated items, and tasks that fail to cover stated requirements. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md so teams catch these issues before writing code. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecified requirements, terminology drift, and conflicting requirements across the three core spec-kit artifacts. - Coverage Mapping: Builds a requirements-to-tasks coverage map, flagging requirements with zero tasks and tasks with no mapped requirement. - Constitution Validation: Checks artifacts against the project constitution (.specify/memory/constitution.md), treating MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit.tasks to generate tasks.md, run this analysis to receive a structured report with severity-ranked findings, coverage metrics, and recommended next actions before invoking /speckit.implement. ## Quick Start Ask the assistant to run the speckit-analyze command to check the current feature's spec, plan, and tasks for inconsistencies and coverage gaps.

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-kit artifacts 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 conflicts ranked by severity.

What does the spec-kit analyze command detect?

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.

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 any required artifact is missing, directing you to the prerequisite command.

Does speckit-analyze modify my spec or task files?

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

How are constitution violations handled in the 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.