One-click install
npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-analyze-demersonpolli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/demersonpolli/basic-interpreter/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-analyze-demersonpolli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents implementation thrash by identifying contradictions, duplications, ambiguities, and missing coverage across your three core planning artifacts before you start building.

Core Features & Use Cases

  • Cross-artifact consistency checks: Compares spec.md, plan.md, and tasks.md to find terminology drift, conflicts, and duplicated or conflicting requirements.
  • Coverage and traceability mapping: Builds an inventory of requirements/success criteria and verifies whether tasks actually cover buildable work.
  • Constitution alignment validation: Detects and prioritizes violations of non-negotiable MUST principles from .specify/memory/constitution.md, treating them as CRITICAL.

Quick Start

Run speckit-analyze after /speckit.tasks completes, and include any optional focus areas in your arguments.

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

Cross-artifact consistency checks compare spec.md, plan.md, and tasks.md to identify terminology drift, duplicated requirements, and conflicts. Running this analysis after task generation reduces planning-to-implementation mismatches by catching inconsistencies early.

How do I verify buildable task coverage for my project requirements?

Coverage and traceability mapping builds an inventory of requirements and success criteria, verifying whether tasks in tasks.md actually cover buildable work. This exposes missing coverage gaps before development starts.

Can I validate plan.md alignment against a constitution.md file?

Constitution alignment validation detects and prioritizes violations of non-negotiable MUST principles from .specify/memory/constitution.md. Violations are treated as CRITICAL severity issues in the structured Markdown report.

What's the best way to find duplicated or ambiguous requirements across planning artifacts?

Non-destructive cross-artifact analysis detects duplication, ambiguity, and underspecification across spec.md, plan.md, and tasks.md. It assigns severity levels to each detected issue and outputs a structured Markdown report for review.

Does the consistency analysis modify my spec.md, plan.md, or tasks.md files?

The analysis satisfies a read-only constraint, meaning it performs non-destructive checks across spec.md, plan.md, and tasks.md. Your planning artifacts remain unchanged while it builds a semantic model to detect inconsistencies.