speckit-analyze

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

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-analyze-empoweredhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/EmpoweredHouse/accrete/tree/main/skills/speckit-analyze
Command: npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-analyze-empoweredhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md before implementation.

Core Features & Use Cases

  • Cross-artifact consistency checks across spec, plan, and tasks to surface duplications, ambiguities, and underspecified items.
  • Coverage mapping linking tasks to requirements and stories to ensure traceability and completeness.
  • Optional remediation guidance generated after analysis to inform improvements without applying changes by default.

Quick Start

After tasks.md is complete, run speckit-analyze to validate alignment across 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 across spec, plan, and tasks files?

To check cross-artifact consistency, run an analysis tool that identifies inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md before implementation begins.

How do I trace requirements coverage and gaps in my project artifacts?

Requirements traceability and coverage mapping are achieved by linking tasks to requirements and stories, ensuring completeness and surfacing coverage gaps by validating principles against a constitution.md file.

When should I run consistency analysis on my specification documents?

Consistency analysis should be run after a complete tasks.md exists to validate alignment across spec.md, plan.md, and tasks.md, ensuring all artifacts are checked before implementation starts.

Can I generate a remediation plan for spec inconsistencies without modifying source artifacts?

Yes, you can generate optional remediation guidance after analysis to inform improvements, operating in a strictly read-only mode to avoid modifying source artifacts like spec.md or plan.md.

What is the best way to find duplications and ambiguities in software requirements?

The best way to find duplications and ambiguities in software requirements is using an automated analysis tool that cross-references spec.md, plan.md, and tasks.md to surface alignment issues.

Does cross-artifact analysis validate project principles and constitution rules?

Yes, cross-artifact analysis uses .specify/memory/constitution.md for principle validation, ensuring your specification, plan, and tasks align with established project rules and identifying coverage gaps.