speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-analyze-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-analyze
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-analyze-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires .specify/scripts/bash/check-prerequisites.sh.

What problem does it solve?

This Skill detects inconsistencies, duplications, ambiguities, and underspecification across spec.md, plan.md, and tasks.md before implementation, so you can fix issues early.

Core Features & Use Cases

  • Cross-artifact consistency analysis: Compares functional requirements, success criteria, architecture/constraints, and task coverage for contradictions and missing mappings.
  • Quality-focused detection passes: Finds duplication, ambiguity, underspecified items, coverage gaps, and terminology drift with bounded output for review.
  • Constitution-aligned guardrails: Validates against .specify/memory/constitution.md and treats MUST conflicts as critical.

Quick Start

Run the speckit-analyze command after your tasks.md has been generated to produce a structured analysis report.

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, plan, and tasks files for consistency before implementation?

Cross-artifact consistency analysis compares spec.md, plan.md, and tasks.md to detect contradictions, missing requirement mappings, and coverage gaps. Running this validation after tasks generation produces a structured report highlighting inconsistencies before you write any code.

What types of quality issues can I detect across spec.md and tasks.md?

Quality-focused detection passes identify duplication, ambiguity, underspecified items, coverage gaps, and terminology drift across your spec documents. It assigns severity levels to each detected issue and generates bounded markdown output for efficient review.

Do I need a generated tasks.md file before running consistency analysis?

Yes, prerequisite checks via check-prerequisites.sh enforce a tasks requirement before execution. Your Spec-kit project must have spec.md, plan.md, and tasks.md generated, plus .specify/memory/constitution.md for aligned guardrails.

Can I validate spec-kit artifacts without modifying my project files?

Yes, strict read-only execution performs non-destructive cross-artifact analysis without modifying files. It validates requirement and task mappings, checks conformance, and outputs a token-efficient markdown report preserving your original artifacts.

How does constitution.md affect consistency validation severity levels?

Constitution-aligned guardrails validate your spec artifacts against .specify/memory/constitution.md and treat MUST conflicts as critical severity. This ensures your architecture constraints and functional requirements conform to established project governance.

What is the best way to find requirement coverage gaps in Spec-kit projects?

Requirement and task mapping analysis detects coverage gaps by comparing functional requirements and success criteria against generated tasks. Optional extension hooks in .specify/extensions.yml allow bounded output for targeted review of missing mappings.