doc-bdd

Generate Layer-4 BDD test scenarios in Gherkin Given-When-Then format.

16|3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-bdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-bdd
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-bdd
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-bdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates Behavior-Driven Development (BDD) test scenarios that formalize requirements into executable Given-When-Then steps, bridging the gap between requirements and test automation.

Core Features & Use Cases

  • Write Feature files with scenarios and background steps
  • Tag scenarios for traceability to REQ and ADR
  • Prepare data-driven scenario outlines for coverage

Quick Start

Create a BDD file with a Feature and several Scenarios linked to REQ IDs and ADRs.

Frequently Asked Questions about doc-bdd

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

FAQPage Schema
How do I write BDD test scenarios in Gherkin format?

BDD test scenarios in Gherkin use Given-When-Then syntax to express behavior as executable steps. This Skill automates creation of Feature files with Scenario and Scenario Outline blocks, Background steps, and traceability tags linked to requirements and architectural decisions.

What is the relationship between BDD scenarios and requirements traceability?

BDD scenarios bridge requirements and tests by tagging each scenario with REQ IDs and ADR references, ensuring every test traces back to a requirement or architectural decision. This Skill enforces explicit traceability tags and Document Control sections for compliance.

Can I use BDD scenarios for data-driven testing?

Yes. This Skill supports Scenario Outline blocks with parameterized data tables, enabling data-driven test coverage. Multiple test cases execute the same scenario logic with different input and expected output values.

What workflow context should I have before creating BDD scenarios?

BDD scenarios work best when upstream Business Requirements Documents (BRD), Product Requirements Documents (PRD), and EARS requirement specifications already exist. This Skill integrates into SDD workflows where requirements and architectural decisions are documented.

How do I ensure my BDD scenarios cover success, error, and edge cases?

This Skill enforces scenario-type coverage by requiring distinct Scenario blocks for success paths, error conditions, and edge cases. Tagging each type ensures comprehensive functional requirement validation within a single Feature file.

What format and structure do BDD Feature files require?

Feature files require Feature declarations, optional Background steps, and Scenarios with Given-When-Then steps. This Skill enforces mandatory Document Control sections, explicit REQ and ADR tags, and Gherkin syntax validation for automation readiness.