spec-validator

Validate implementations against specifications by checking requirements coverage, acceptance criteria, and documentation updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill spec-validator-fractary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-validator
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/spec/skills/spec-validator
Command: npx skills add https://github.com/fractary/claude-plugins --skill spec-validator-fractary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, grep, sed, and includes scripts (resource) components.

What problem does it solve?

This Skill validates implementations against specs by checking requirements coverage, acceptance criteria, file changes, tests, and documentation updates.

Core Features & Use Cases

  • Requirements coverage: Verifies all requirements are addressed
  • Acceptance criteria: Checks checkbox completion
  • Documentation updates: Ensures docs reflect changes

Quick Start

Validate a spec against its implementation to determine readiness for archival.

Frequently Asked Questions about spec-validator

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

FAQPage Schema
How do I validate that an implementation meets its specification requirements?▼

Specification validation checks whether your implementation addresses all requirements, acceptance criteria, and documentation updates outlined in the spec. This Skill parses the spec, verifies acceptance criteria completion, confirms modified files align with requirements, and ensures tests and documentation have been updated accordingly.

What does acceptance criteria validation actually check?▼

Acceptance criteria validation confirms that checkboxes and conditions defined in your specification are met by the implementation. It verifies each criterion is addressed, preventing incomplete implementations from progressing to archival.

How do I know if my code changes, tests, and documentation are complete against a spec?▼

This Skill assesses implementation readiness by computing a validation score across requirements coverage, test additions, and documentation updates. It updates the spec frontmatter with status, giving you a clear signal whether the implementation satisfies the spec.

Can I use this during my specification review workflow?▼

Yes, this Skill integrates into spec validation workflows, particularly during the FABER Evaluate phase. It takes a spec path and issue reference, then validates changes and updates against that specification context.

What file formats and tools does specification validation require?▼

Specification validation uses bash scripting, jq for JSON parsing, grep for pattern matching, and sed for text processing. It works with spec files containing YAML frontmatter and markdown content to parse requirements and acceptance criteria.

What happens if my implementation doesn't cover all acceptance criteria?▼

The validation score reflects incomplete coverage, and the spec frontmatter status is updated to indicate gaps. This prevents premature archival and highlights which acceptance criteria remain unaddressed.