speckit-analyze

Validate cross-artifact alignment among spec.md, plan.md, and tasks.md.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/chuanyue98/prompt-gallery --skill speckit-analyze-chuanyue98
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/chuanyue98/prompt-gallery/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/chuanyue98/prompt-gallery --skill speckit-analyze-chuanyue98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents implementation thrash by detecting contradictions, duplications, ambiguities, and coverage gaps between the spec, plan, tasks, and constitution after task generation.

Core Features & Use Cases

  • Cross-artifact consistency analysis: Compares spec.md, plan.md, and tasks.md to surface terminology drift, ordering conflicts, and missing alignments.
  • Constitution-aligned validation: Flags anything that conflicts with MUST principles defined in .specify/memory/constitution.md.
  • Coverage and completeness checks: Reports requirements with zero task coverage and tasks that don’t map cleanly to requirements or user stories.

Quick Start

Run the speckit-analyze command after you have successfully produced a complete tasks.md so it can generate a structured Markdown analysis report.

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 between spec, plan, and tasks files?

Cross-artifact consistency analysis compares spec.md, plan.md, and tasks.md to detect duplication, ambiguity, and coverage gaps. It produces a token-efficient Markdown report without modifying files.

When do I need to run cross-artifact alignment validation for requirements?

Cross-artifact alignment validation should run immediately after tasks generation. This ensures implementation readiness by verifying buildable requirements and measurable success criteria before development.

How do I validate generated tasks against constitution principles?

Constitution-aligned validation flags anything conflicting with MUST principles defined in .specify/memory/constitution.md. It checks tasks and requirements against these rules to prevent implementation thrash.

Can I find requirements with zero task coverage in my markdown docs?

Coverage and completeness checks identify requirements with zero task coverage and tasks that don’t map cleanly to requirements or user stories. This exposes gaps across spec, plan, and tasks files.

Does the spec, plan, and tasks analysis modify my source files?

No, consistency analysis requires read-only execution. It uses a PowerShell script to resolve directories and docs, producing a structured Markdown report while keeping source files unmodified.