speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and quality gaps.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-analyze-omerkllm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/omerkllm/edris-antigravity/tree/main/.cursor/skills/speckit-analyze
Command: npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-analyze-omerkllm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-artifact quality checks to identify inconsistencies among spec.md, plan.md, and tasks.md in Speckit workflows, ensuring alignment before execution.

Core Features & Use Cases

  • Consistency checks across FRs, plans, and tasks to surface misalignments.
  • Ambiguity and placeholder detection to prevent vague requirements.
  • Constitution compliance verification against project guidelines.

Quick Start

Run the speckit-analyze command to generate the analysis report against spec.md, plan.md, and tasks.md.

Frequently Asked Questions about speckit-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check cross-artifact consistency between spec.md, plan.md, and tasks.md?

To check cross-artifact consistency, you can run an analysis that reads spec.md, plan.md, and tasks.md to identify misalignments, conflicts, and coverage gaps. The process outputs a structured report highlighting duplications and ambiguities across your workflow.

What is cross-artifact quality analysis in Speckit workflows?

Cross-artifact quality analysis is the process of identifying inconsistencies and quality gaps among spec.md, plan.md, and tasks.md. It ensures alignment before execution by applying checks against the .specify/memory constitution to verify project guideline compliance.

How do I detect ambiguities and placeholder text in my spec.md and plan.md files?

You can detect ambiguities and placeholders by running a consistency check across your spec.md and plan.md files. This analysis surfaces vague requirements and prevents execution issues by flagging undefined terms in a structured report.

Does Speckit constitution compliance verification work with existing tasks.md files?

Yes, constitution compliance verification works with existing tasks.md files by applying the .specify/memory constitution to your current artifacts. It checks your tasks against project guidelines to ensure alignment and surfaces any compliance gaps.

What is the best way to find coverage gaps between functional requirements and tasks?

The best way to find coverage gaps is to run a cross-artifact analysis that compares functional requirements in spec.md against tasks.md. This identifies missing implementations and outputs a structured report highlighting conflicts and uncovered requirements.

Why do my spec.md and plan.md files have conflicting requirements during execution?

Conflicting requirements occur when spec.md and plan.md contain misaligned definitions. Running a cross-artifact consistency check identifies these conflicts and duplications, ensuring alignment before execution and preventing downstream implementation errors.