speckit-analyze

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AstralDeep/astralprojection-flutter --skill speckit-analyze-astraldeep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/AstralDeep/astralprojection-flutter/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/AstralDeep/astralprojection-flutter --skill speckit-analyze-astraldeep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies inconsistencies, ambiguities, and gaps across spec.md, plan.md, and tasks.md to improve alignment before implementation.

Core Features & Use Cases

  • Detect duplication, vague requirements, and missing coverage across the three core artifacts.
  • Map findings to functional requirements, user stories, and tasks to support traceability.
  • Produce a remediation-ready report with prioritized issues and suggested amendments.

Quick Start

After you generate tasks.md, run the speckit-analyze workflow to produce a structured report on cross-artifact quality.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check for inconsistencies across spec.md, plan.md, and tasks.md?

You can identify cross-artifact inconsistencies by analyzing spec.md, plan.md, and tasks.md to detect coverage gaps, ambiguities, and duplication, which produces a structured report mapping findings to functional requirements and associated tasks.

What is cross-artifact analysis in software specification projects?

Cross-artifact analysis is the process of scanning spec.md, plan.md, and tasks.md to detect missing coverage, vague requirements, and duplication, ensuring full traceability between functional requirements and generated tasks before implementation begins.

When do I need to run a cross-artifact consistency check?

You need to run a cross-artifact consistency check immediately after task generation in your SpeckKit project to ensure the newly created tasks.md fully aligns with the functional requirements in spec.md and the technical plan.md.

Does the analysis workflow modify the spec, plan, or tasks files?

The analysis workflow strictly avoids modifying any artifacts during the review process, operating as a read-only check that solely produces a structured report containing prioritized issues and suggested amendments for manual remediation.

How do I map detected ambiguities to functional requirements and tasks?

You map detected ambiguities to functional requirements and tasks by running an analysis workflow that evaluates the relationships across spec.md, plan.md, and tasks.md, outputting a remediation-ready report with prioritized issues and traceability links.