spec-validator

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.

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.

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.

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.

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.