spec-validator

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

Updated May 6, 2026

Search Tags:#software engineering #traceability #specification validation #consistency checking #software requirements

Ready to run

npx skills add https://github.com/crgarcia12/compy --skill spec-validator-crgarcia12

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-validator
Source: https://github.com/crgarcia12/compy/tree/main/.github/skills/spec-validator
Command: npx skills add https://github.com/crgarcia12/compy --skill spec-validator-crgarcia12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit automates the validation of specification consistency and traceability across PRD, FRD, and Gherkin files, detecting gaps, orphans, contradictions, and missing coverage.

Core Features & Use Cases

Consistency Checking: Validates that all requirements are traceable across different specification documents.
Gap Detection: Identifies missing or untraceable requirements.
Contradiction Reporting: Flags conflicting requirements across documents.
Use Case: Use this Skill unit in software development to ensure that the PRD aligns with the FRD and the FRD aligns with the implemented Gherkin scenarios.

Quick Start

Run the spec-validator skill to validate your project specifications and check for consistency.

Frequently Asked Questions about spec-validator

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

FAQPage Schema

How do I check traceability between PRD, FRD, and Gherkin files?▼

Traceability validation works by parsing text and matching patterns across PRD, FRD, and Gherkin files to detect gaps, contradictions, and missing coverage between your software requirements specifications.

How do I detect contradictions and gaps in software requirements specifications?▼

Detect contradictions and gaps in software requirements specifications by automating consistency checking across documents, flagging conflicting requirements, and identifying missing or untraceable items in your PRD and FRD.

What is the best way to automate consistency checking for software requirements?▼

Automating consistency checking for software requirements is best done by validating that PRD aligns with FRD and FRD aligns with implemented Gherkin scenarios, ensuring full traceability and completeness.

Do I need any specific dependencies to run specification validation?▼

You do not need any external dependencies to run specification validation. The Skill operates independently using its built-in scripts and references to parse your PRD, FRD, and Gherkin files for consistency checking.

Can I validate Gherkin scenarios against my FRD for missing coverage?▼

Yes, you can validate Gherkin scenarios against your FRD for missing coverage. The Skill detects gaps and untraceable requirements by ensuring functional specifications align directly with implemented behavioral scenarios.

When should I use automated spec validation instead of manual review?▼

Use automated spec validation instead of manual review when you need to ensure traceability and completeness across multiple PRD, FRD, and Gherkin documents, efficiently catching contradictions and missing coverage that manual checks easily miss.