spec-validator

Validate consistency and traceability across PRD, FRD, and Gherkin specifications.

Updated Mar 30, 2026

Search Tags:#code quality #traceability #requirements management #specification validation #product lifecycle

Ready to run

npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill spec-validator-emeaappgbb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-validator
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/spec-validator
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill spec-validator-emeaappgbb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that all specifications in the product lifecycle (PRD → FRD → Gherkin) are consistent and traceable, detecting gaps, orphans, contradictions, and missing coverage.

Core Features & Use Cases

Traceability: Verify that every requirement is traced from PRD to FRD to Gherkin.
Consistency: Detect gaps, orphans, contradictions, and missing coverage.
Use Case: Before deploying to Azure, use this Skill to validate that all requirements are met and that there are no inconsistencies in the specification chain.

Quick Start

Run the spec-validator skill to validate the consistency of your specifications.

Frequently Asked Questions about spec-validator

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

FAQPage Schema

How do I validate spec consistency and traceability across the product lifecycle?▼

To validate spec consistency and traceability across the product lifecycle, you can run a validation process on your specification chain to detect gaps, orphans, contradictions, and missing coverage from PRD to FRD to Gherkin. This ensures requirements are fully traced before any human gate review.

What is specification validation and when do I need to run it?▼

Specification validation is the process of verifying traceability across the PRD, FRD, and Gherkin chain. You need to run it before human gate reviews, before end-to-end or Gherkin generation, after resuming work, or after applying human edits to any spec file to prevent missing coverage.

How do I detect gaps and contradictions between PRD, FRD, and Gherkin files?▼

To detect gaps and contradictions between PRD, FRD, and Gherkin files, run a specification validation check across the document chain. This process identifies orphaned requirements, contradictions, and missing coverage to maintain product lifecycle consistency.

Can I check requirements management traceability before generating Gherkin features?▼

Yes, you can check requirements management traceability before generating Gherkin features. Validating the specification chain beforehand ensures that every requirement is properly traced from PRD to FRD, preventing missing coverage in the generated Gherkin files.

Why does my specification chain have orphaned requirements after human edits?▼

Your specification chain has orphaned requirements because human edits to spec files can break the traceability links between PRD, FRD, and Gherkin. Running a specification validation check after edits detects these orphans, gaps, and contradictions.