speckit-analyze

To check spec, plan, and tasks consistency before implementation, analyze spec.md, plan.md, and tasks.md for requirement coverage, plan-task alignment, and validation gaps. This non-destructive review produces a traceability report with findings and risk summaries.

Spec-kit workflow blockers during stage continuation occur when plan decisions are unsupported or validation is weak. Analyzing the spec, plan, and tasks artifacts detects missing artifacts and workflow gate risks to prevent these blockers.

The best way to detect validation gaps in spec-kit feature workflows is to perform a layered consistency review across spec.md, plan.md, and tasks.md. This flags weak validation and confirms task breakdowns fully cover intended behavior.

Yes, you can review requirement coverage without modifying source artifacts by applying a non-destructive audit to spec.md, plan.md, and tasks.md. This validates traceability and alignment while leaving the original feature files unchanged.

Yes, spec analysis flags missing artifacts in plan-task alignment by comparing requirements, implementation slices, and task breakdowns. It detects unsupported plan decisions and produces a reviewer-friendly analysis report with next-step guidance.

You need layered artifact traceability for spec.md and tasks.md when a spec-kit feature is ready for coding and requires a non-destructive audit. This ensures the plan and tasks fully cover the intended behavior before implementation begins.