speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and ambiguities.

4|11|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-analyze-obsidian-owl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-analyze-obsidian-owl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams proactively identify inconsistencies, duplications, ambiguities, and gaps across spec.md, plan.md, and tasks.md after task generation, preventing misalignment before implementation.

Core Features & Use Cases

  • Cross-artifact analysis detects duplicates, ambiguities, and underspecifications across spec, plan, and tasks.
  • Constitution alignment checks verify alignment with project principles and rules defined in the constitution.
  • Remediation planning suggests improvements and maps findings to requirements for follow-up.

Quick Start

Run the speckit-analyze analysis after the speckit.tasks phase to produce a structured report.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I detect inconsistencies across spec, plan, and tasks files?

Apply a cross-artifact analysis after generating tasks.md to identify inconsistencies, duplications, ambiguities, and underspecifications across spec.md, plan.md, and tasks.md before implementation.

When should I check for alignment between spec, plan, and tasks documents?

You should check for alignment immediately after the task generation phase produces tasks.md, ensuring your spec.md and plan.md match the tasks before starting any implementation across projects.

How do I validate project tasks against a constitution or governance rules?

Validate tasks against governance rules by loading the constitution during analysis to verify alignment with project principles, outputting a report with prioritized remediation candidates.

Does cross-artifact analysis modify the spec, plan, or tasks files?

No, cross-artifact analysis enforces read-only analysis on spec.md, plan.md, and tasks.md. It outputs a compact report with remediation suggestions without modifying your original files.

What is the best way to find underspecifications in project planning documents?

The best way to find underspecifications is to run an automated cross-artifact analysis that maps findings to requirements and suggests improvements, helping teams remediate gaps proactively.