skills.rest
kaiohenricunha
kaiohenricunhaCOMMUNITY
Explore all skills by this author →
𝕏@kaiohenricunhaGitHub

validate-spec

Audit implemented spec artifacts against the codebase and generate evidence-based reports.

Updated Apr 14, 2026
Search Tags:#spec-driven development#acceptance testing#implementation audit#codebase verification#spec validation#constraint checking#audit reporting
One-click install
npx skills add https://github.com/kaiohenricunha/dotbabel --skill validate-spec-kaiohenricunha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-spec
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/validate-spec
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill validate-spec-kaiohenricunha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When using spec-driven development, it is common for specs to be marked as complete even when implementation is partial, missing, or misaligned with documented requirements. Manual checks are time-consuming, prone to human error, and often lack concrete evidence to back up claims. This skill eliminates that guesswork by performing a rigorous, evidence-based audit of implemented specs against the actual codebase, giving you an objective, verifiable report of what is actually built.

Core Features & Use Cases

  • Constraint Evidence Auditing: Walks every tagged constraint (ARCH, PERF, KD, etc.) in the spec and grounds each verdict in concrete file:line evidence from the codebase, classifying constraints as Implemented, Partial, Unverified, or N/A.
  • Acceptance Command Validation: Executes the spec's defined acceptance commands, uses git stash round-trips to distinguish pre-existing failures from failures introduced by the spec implementation, and records full output and duration for each command.
  • Standardized Audit Reporting: Generates a consistent, structured audit document in docs/audits/ covering structural metadata checks, constraint coverage, acceptance results, and severity-classified issues, with no modifications to the original spec files.
  • Use Case: For engineering teams using the /spec format for spec-driven development, run this skill after implementing a spec to get an objective closure report before marking the spec as done, catching missing features, broken tests, and spec-code drift early.

Quick Start

Use the validate-spec skill to audit the implementation of your target spec ID and generate a complete evidence-based validation report in your project's docs/audits/ directory.

Frequently Asked Questions about validate-spec

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

FAQPage Schema
How do I audit if my codebase matches spec-driven development requirements?▼

To audit spec-driven development requirements, you can validate implemented structured spec artifacts against your codebase to verify implementation completeness. This checks constraint evidence and acceptance command execution results, generating an evidence-based audit report with file:line citations.

How does acceptance testing validation distinguish pre-existing failures from new ones?▼

Acceptance testing validation distinguishes pre-existing failures by using git stash round-trips during command execution. This mechanism isolates whether test failures were introduced by the spec implementation or already existed in the codebase, recording full output and duration for each command.

What is the best way to verify implementation completeness for a structured spec?▼

The best way to verify implementation completeness is by auditing tagged constraints against concrete codebase evidence. This process grounds each verdict in file:line citations, classifying constraints as Implemented, Partial, Unverified, or N/A to ensure objective spec-code alignment.

Can I use constraint checking without modifying my original spec files?▼

Yes, constraint checking generates a standardized audit document in the docs/audits/ directory without modifying the original spec files. The audit report covers structural metadata checks, constraint coverage, acceptance results, and severity-classified issues independently.

Why does spec-code drift occur and how do I catch it early?▼

Spec-code drift occurs when specs are marked complete despite partial or misaligned implementations. Catch it early by running an evidence-based audit after implementation to objectively verify documented requirements against the actual codebase before closure.

When do I need spec validation in my engineering workflow?▼

You need spec validation after implementing a spec but before marking it as done. It provides an objective closure report by catching missing features, broken tests, and spec-code drift through rigorous evidence-based auditing of constraint coverage and acceptance commands.

Related Skills

Explore More Software Engineering Skills→
Rubiss-ProjectsRubiss-Projects
25

speckit-git-remote

Detect the Git remote URL for GitHub integration in spec-kit projects.

Official
Basic
joshsmithxrmjoshsmithxrm
5

spec-audit

Audit specifications against codebases to identify drift, gaps, and undocumented behavior.

Community
Advanced
japurcelljapurcell

issue-to-spec

Convert GitHub issues into planning-ready specs with acceptance criteria.

Community
Advanced
vuminhieuvuminhieu

web-design-guidelines

Audit UI code against Web Interface Guidelines and report file:line findings.

Community
Intermediate