skills.rest
vnovakovits
vnovakovitsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

behavior-driven-development

Guides collaborative BDD practice using Gherkin scenarios, Three Amigos discovery, and outside-in TDD.

1|Updated May 21, 2026
Search Tags:#testing#tdd#acceptance criteria#bdd#Gherkin#Cucumber#specification by example
One-click install
npx skills add https://github.com/vnovakovits/claude-skills --skill behavior-driven-development-vnovakovits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: behavior-driven-development
Source: https://github.com/vnovakovits/claude-skills/tree/main/plugins/engineering-practices/skills/behavior-driven-development
Command: npx skills add https://github.com/vnovakovits/claude-skills --skill behavior-driven-development-vnovakovits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Requirements often drift between business intent and implementation, and teams frequently misuse tools like Cucumber as brittle UI-testing frameworks. This Skill provides the vocabulary and practices of Behavior-Driven Development so features are specified collaboratively, captured as concrete examples, and automated as living documentation. ## Core Features & Use Cases - Discovery & Formulation Guidance: Applies the Three Amigos workshop, Example Mapping, and Feature Injection to surface assumptions and agree on behavior before code is written. - Gherkin Scenario Authoring: Enforces declarative, domain-language scenarios with one When per scenario, realistic examples, and independence between scenarios. - Outside-In TDD Pairing: Connects acceptance-level BDD scenarios to inner TDD loops so one failing scenario drives many unit-level cycles until the feature ships. - Use Case: When starting a new feature like online table reservations, run a Three Amigos session, write Gherkin scenarios for capacity rules, then drive implementation outside-in until the scenarios pass on every build. ## Quick Start Ask Claude to help you write BDD Gherkin scenarios and acceptance criteria for the new feature you are about to build.

Frequently Asked Questions about behavior-driven-development

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

FAQPage Schema
How do I write good Gherkin scenarios for BDD?▼

Write declarative scenarios that express intent rather than UI mechanics, using the domain's ubiquitous language. Keep one When step per scenario, use concrete realistic data, make scenarios independent, and describe what the system does rather than how it does it.

What is the difference between BDD, TDD, and ATDD?▼

TDD is developer-facing and drives unit-level design, while BDD is stakeholder-facing and drives feature-level specification through collaborative discovery. ATDD resembles BDD's outer acceptance loop; modern BDD subsumes ATDD's automation discipline and adds discovery and ubiquitous-language emphasis.

Which BDD tool should I use for my tech stack?▼

Cucumber serves Ruby and JavaScript, Reqnroll is the current open-source choice for .NET after SpecFlow was archived, Behave covers Python, JBehave covers Java, and Behat covers PHP. Tooling is the smallest decision; the collaborative practice matters most.

Why is my Cucumber test suite brittle and slow?▼

Brittleness usually comes from imperative scenarios coupled to UI element IDs, CSS selectors, and click sequences. Rewrite scenarios declaratively around business intent, push mechanics into step definitions, and ensure a Three Amigos conversation precedes automation.

When should I not use BDD?▼

Avoid BDD for shallow CRUD domains, rapid prototypes without stable behavioral specifications, or when business stakeholders cannot participate. Without stakeholder collaboration, BDD degrades into developers writing slow tests in Gherkin, which is the worst of both worlds.

Related Skills

Explore More Software Engineering Skills→
Serg28Serg28

feature-forge

Facilitate requirements workshops and generate EARS-format specification documents.

Community
Intermediate
bitpantrybitpantry

tdd-workflow

Automate TDD workflows for bug fixes, features, and regression remediation.

Community
Advanced
zenbuappszenbuapps

aibdd.auto.php.it.code-quality

Standardize PHP WordPress integration test quality with SOLID and 3-layer architecture.

Official
Advanced
ymkzymkz

japanese-test-naming

Enforce Japanese Given-When-Then test naming conventions across Java, Kotlin, and TypeScript projects.

Community
Basic