speckit-analyze

Analyze spec.md, plan.md, and tasks.md for cross-artifact inconsistencies.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill speckit-analyze-ldilov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/ldilov/harness-forge --skill speckit-analyze-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-artifact inconsistency, duplication, and underspecification across spec.md, plan.md, and tasks.md are identified and reported to prevent misalignment before implementation.

Core Features & Use Cases

  • Automated cross-artifact consistency checks across spec.md, plan.md, and tasks.md
  • Detection of duplicates, ambiguities, and underspecifications with actionable remediation suggestions
  • Constitution alignment verification against .specify/memory/constitution.md
  • Generated structured analysis reports and optional remediation planning
  • Strict read-only analysis to avoid unintended edits

Quick Start

Run speckit-analyze from the repository root after speckit.tasks has produced a complete 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 spec.md, plan.md, and tasks.md for inconsistencies before implementation?

To check spec.md, plan.md, and tasks.md for inconsistencies, you can run a cross-artifact analysis from the repository root. This detects duplicates, ambiguities, and underspecifications to prevent misalignment before you start coding.

What is cross-artifact consistency analysis in speckit governance?

Cross-artifact consistency analysis in speckit governance verifies alignment across spec.md, plan.md, and tasks.md. It identifies duplication and underspecification, ensuring all project artifacts match the defined constitution before implementation begins.

Does speckit-analyze modify my spec.md or plan.md files during consistency checks?

No, speckit-analyze enforces strict read-only constraints during consistency checks. It avoids unintended edits to spec.md, plan.md, and tasks.md, providing a formal analysis report and optional remediation planning without modifying your files.

How do I detect ambiguities and underspecifications across project artifacts?

You can detect ambiguities and underspecifications across project artifacts by running an automated analysis on your spec.md, plan.md, and tasks.md. This process generates actionable remediation suggestions to resolve the identified issues.

When do I need to run a cross-artifact alignment audit?

You need to run a cross-artifact alignment audit after speckit.tasks has produced a complete tasks.md. This iterative check ensures your spec.md, plan.md, and tasks.md are fully aligned and constitution-validated before entering the implementation phase.

Can I verify constitution alignment against my project memory?

Yes, you can verify constitution alignment against .specify/memory/constitution.md. The analysis checks your spec.md, plan.md, and tasks.md files against this constitution to ensure governance compliance before implementation.