speckit-analyze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves ambiguity and fragmentation in development projects by performing a cross-artifact consistency check between specifications, plans, and task lists.

Core Features & Use Cases

  • Consistency Validation: Detects terminology drift and conflicting requirements across core project documents.
  • Coverage Analysis: Identifies requirements that lack corresponding implementation tasks and flags unmapped tasks.
  • Constitution Enforcement: Automatically validates project artifacts against defined memory principles to ensure compliance.

Quick Start

Run the speckit-analyze command to perform a comprehensive consistency check on your current project 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 project documentation for consistency and ambiguity?

To check project documentation for consistency, you can perform a cross-artifact analysis across spec.md, plan.md, and tasks.md to detect terminology drift, conflicting requirements, and underspecified elements.

What is cross-artifact consistency analysis in software engineering?

Cross-artifact consistency analysis evaluates your project's specifications, plans, and task lists to identify duplication, ambiguity, and underspecification, ensuring all documents align and maintain overall project quality.

How do I validate that my project tasks match the specified requirements?

You validate that project tasks match requirements by running a coverage analysis that identifies requirements lacking corresponding implementation tasks and flags any unmapped tasks within your documentation.

Do I need a specific directory structure to analyze spec-kit project artifacts?

Yes, you need a valid spec-kit project structure containing a .specify directory to execute the validation logic and evaluate your artifacts against defined memory principles.

How do I enforce constitution alignment across project specifications and plans?

You enforce constitution alignment by automatically validating project artifacts against defined memory principles, ensuring full compliance and preventing fragmentation between your specifications and plans.

What happens if my project documentation has terminology drift between specs and tasks?

If terminology drift exists between specs and tasks, the consistency validation detects these conflicting requirements and flags the fragmentation, allowing you to resolve the ambiguity before implementation.