What happens if a document fails validation?

The skill generates a detailed Validation Report listing specific error codes (like BDD-E010 for syntax errors) and warnings (like BDD-W002 for missing tags) to help the user fix the issues.

How does it handle traceability?

The skill checks for specific cumulative tags like @brd, @prd, and @ears to ensure every BDD scenario is mapped back to its parent business and product requirements.

Can I validate standard .feature files with this skill?

Yes, the validator supports both specialized Markdown-based BDD documents and standard Gherkin .feature files typically used in testing frameworks.

What is the purpose of the doc-bdd-validator skill?

It is designed to validate BDD documentation against specific structural and content standards, ensuring they are complete, correctly formatted in Gherkin, and properly linked to upstream requirements.

What does the ADR-Ready score represent?

The ADR-Ready score is a quality metric (threshold 90%) that evaluates scenario coverage, step clarity, data completeness, and traceability to determine if a BDD document is ready for architectural review.

BDD Document Validator

Name: BDD Document Validator
Author: vladm3105

byvladm3105

•

Learning & Documentation

Validates Behavior-Driven Development (BDD) documents against Layer 4 schema standards to ensure structural integrity and Gherkin syntax compliance.

About

The BDD Document Validator is a specialized skill designed to enforce quality and consistency across Behavior-Driven Development artifacts within the AI Doc Flow Framework. It automatically checks BDD documents for mandatory metadata, specific document structures (including Document Control and Traceability sections), and correct Gherkin syntax. By calculating an 'ADR-Ready' score based on scenario coverage and data completeness, it ensures that requirements are mature enough for downstream architectural decisions and test implementations. This skill is essential for teams maintaining high-compliance documentation where traceability between business rules and technical scenarios is critical.

Key Features

Detailed validation reporting with categorized error and warning codes
1 GitHub stars
Mandatory metadata and tag taxonomy verification for Layer 4 artifacts
ADR-Ready quality scoring to benchmark document maturity
Automated traceability checking for @brd, @prd, and @ears references
Comprehensive Gherkin syntax and GWT (Given-When-Then) structure validation

Use Cases

Ensuring BDD documents meet organizational standards before merging into a shared repository
Maintaining rigorous traceability between upstream business requirements and technical BDD artifacts
Validating Gherkin scenarios for consistency before they are consumed by automated testing tools

About

Key Features

Detailed validation reporting with categorized error and warning codes
1 GitHub stars
Mandatory metadata and tag taxonomy verification for Layer 4 artifacts
ADR-Ready quality scoring to benchmark document maturity
Automated traceability checking for @brd, @prd, and @ears references
Comprehensive Gherkin syntax and GWT (Given-When-Then) structure validation

Use Cases

Ensuring BDD documents meet organizational standards before merging into a shared repository
Maintaining rigorous traceability between upstream business requirements and technical BDD artifacts
Validating Gherkin scenarios for consistency before they are consumed by automated testing tools