speckit.validate

Generate a coverage matrix and validate code implementations against specification requirements.

63|13|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.validate
Source: https://github.com/compnew2006/Spec-Kit-Antigravity-Skills/tree/main/skills/speckit.validate
Command: npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that software implementations satisfy specification requirements and acceptance criteria, preventing drift between spec and code.

Core Features & Use Cases

  • Generate a requirements coverage matrix by extracting functional requirements, acceptance criteria, and edge cases from spec.md.
  • Cross-check implemented code references against the requirements based on tasks.md and code changes.
  • Produce a validation report with coverage metrics, uncovered requirements, and actionable recommendations.
  • Integrate with speckit.implement as a prerequisite to ensure end-to-end validation in the Spec-Kit workflow.

Quick Start

Run the validation pipeline against the current feature by executing the validation workflow in your project workspace.

Frequently Asked Questions about speckit.validate

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

FAQPage Schema
How do I validate code implementations against specification requirements?

To validate code implementations against specification requirements, you can automate generation of a requirements coverage matrix from spec.md. The validation cross-checks code changes against tasks.md to produce a report with actionable gaps.

What is spec-to-code validation and how does it prevent drift?

Spec-to-code validation is the automated process of mapping code changes to formal specification requirements to prevent drift. It builds a coverage matrix verifying functional requirements, acceptance criteria, and edge cases are met.

Do I need formal spec.md and tasks.md files to run automated requirements verification?

Yes, automated requirements verification requires formal spec.md and tasks.md files in your project workspace. The validation pipeline extracts functional requirements and acceptance criteria from these files to map code changes.

How do I generate a requirements coverage matrix from spec files?

To generate a requirements coverage matrix from spec files, the validation workflow extracts functional requirements, acceptance criteria, and edge cases from spec.md. It cross-references implemented code based on tasks.md to identify uncovered requirements.

What does a spec validation report include for uncovered requirements?

A spec validation report includes coverage metrics, uncovered requirements, and actionable recommendations for addressing gaps. It maps implemented code references against extracted functional requirements to highlight missing acceptance criteria.