speckit-analyze

Analyze project specification, planning, and task documents for consistency and quality.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common issue of drift between high-level specifications, technical plans, and granular task lists in software development projects, ensuring that implementation remains aligned with the project constitution.

Core Features & Use Cases

  • Cross-Artifact Validation: Automatically detects inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md.
  • Constitution Enforcement: Validates that all project requirements and tasks strictly adhere to the defined project constitution and quality gates.
  • Use Case: Before starting a new development sprint, run this analysis to identify missing task coverage or conflicting requirements that could lead to implementation errors.

Quick Start

Run the speckit-analyze skill to perform a comprehensive consistency check across your current project specification and task artifacts.

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 my project specification, plan, and task documentation?

Specification consistency analysis detects drift between high-level specifications, technical plans, and granular task lists, ensuring implementation remains aligned with your project constitution and defined quality gates.

How do I validate that my project tasks align with the defined constitution and quality gates?

Run a consistency analysis to validate project artifacts against defined success criteria and constraints, enforcing strict adherence to your project constitution principles and identifying coverage gaps.

Do I need a specific directory structure to validate project artifacts and task coverage?

Yes, a structured .specify directory is required to validate project artifacts, as the consistency analysis evaluates cross-artifact alignment and coverage gaps against your defined success criteria and constraints.

When should I run a cross-artifact consistency analysis in my development workflow?

Run consistency analysis before starting a new development sprint to identify missing task coverage, ambiguities, or conflicting requirements early, preventing implementation errors caused by specification drift.

What is the best way to detect inconsistencies and coverage gaps across technical project requirements?

Automated cross-artifact validation is the best way to detect inconsistencies, evaluating alignment with project constitution principles and identifying coverage gaps or ambiguities across specification, planning, and task documentation.