Does Spec Validator update my files?

Yes, it automatically updates the frontmatter of your specification files with validation status, completion dates, and implementation notes.

What happens if my implementation is missing tests?

The skill will return a 'warning' or 'failure' status, provide a detailed analysis of what is missing, and suggest specific fixes to achieve full validation.

Is this skill compatible with the FABER framework?

Yes, it is specifically designed to be invoked during the FABER Evaluate phase or by the spec-manager agent before archiving tasks.

What does the Spec Validator skill do?

It compares your current code changes against a specific markdown specification file to ensure all requirements, tests, and documentation updates are completed.

Spec Validator

Name: Spec Validator
Author: fractary

byfractary

•

Security & Testing

Validates code implementations against technical specifications to ensure requirement coverage, test compliance, and documentation accuracy.

About

The Spec Validator skill automates the critical bridge between planning and production by cross-referencing implementation changes with written specifications. It parses markdown-based spec files to extract requirements and acceptance criteria, then verifies that the expected files were modified, tests were added, and documentation was updated. By generating detailed validation reports and updating spec frontmatter, it ensures that no feature is archived or merged until it fully meets its defined criteria, making it a cornerstone of the FABER Evaluate phase.

Key Features

Structured reporting with success, warning, and failure states
Validation of test coverage and documentation updates
2 GitHub stars
Verification of file modifications against expected implementation scope
Automatic spec frontmatter updates with validation scores and dates
Automated parsing of requirements and acceptance criteria from markdown

Use Cases

Automating the evaluation phase of the FABER development workflow
Ensuring feature completeness before archiving a work item
Checking that documentation and tests were not overlooked during a rapid implementation

About

Key Features

Structured reporting with success, warning, and failure states
Validation of test coverage and documentation updates
2 GitHub stars
Verification of file modifications against expected implementation scope
Automatic spec frontmatter updates with validation scores and dates
Automated parsing of requirements and acceptance criteria from markdown

Use Cases

Automating the evaluation phase of the FABER development workflow
Ensuring feature completeness before archiving a work item
Checking that documentation and tests were not overlooked during a rapid implementation