Behavior Driven Development

Apply Behavior-Driven Development (BDD) by Dan North, Gojko Adzic, Matt Wynne & Aslak Hellesøy, and Liz Keogh — covering the three practices (discovery, formulation, automation), three amigos workshops, Gherkin scenarios, Specification by Example, living documentation, Feature Injection, and pairing BDD with outside-in TDD. Use when starting a new feature, capturing requirements collaboratively, writing acceptance criteria, deciding what scenarios to automate, or fixing a "Cucumber suite" that has become a brittle UI-testing pile.

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill behavior-driven-development
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/behavior-driven-development ~/.claude/skills/behavior-driven-development

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Behavior-Driven Development

Apply BDD when starting a new feature, capturing requirements with business stakeholders, deciding what behavior to specify, writing acceptance criteria, or driving outside-in TDD with executable specifications. The central idea is **collaborative discovery of behavior** — not test syntax, not tooling, not Gherkin.

## Core Philosophy

**BDD is TDD done right.** Dan North coined the term in 2003-2006 after observing that "test-first" misled people into thinking TDD was about testing. He renamed and reframed it around *behavior* and *examples* to recover the original intent: TDD is a way to specify and design software, with tests as a side effect.

**Behavior is the unit of conversation.** Not classes, not methods, not stories — observable, testable behaviors a stakeholder can recognize.

**Examples sharpen requirements.** Abstract requirements ("the system shall...") are ambiguous; concrete examples ("given X, when Y, then Z") expose ambiguity immediately and become the specification.

**Living documentation.** Specifications that are continuously verified by execution stay accurate. Documentation that is not executed rots.

**Collaboration over ceremony.** The hardest, most valuable BDD work is the conversation between business, development, and testing — *before* anyone writes a scenario or a line of code. The Gherkin file is the smallest part.

---

## The Three Practices (Cucumber Book)

BDD has three practices, in order of importance:
Read the full skill on GitHub

Details

Skill name
behavior-driven-development
Path
plugins/engineering-practices/skills/behavior-driven-development/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Behavior Driven Development skill do?

Apply Behavior-Driven Development (BDD) by Dan North, Gojko Adzic, Matt Wynne & Aslak Hellesøy, and Liz Keogh — covering the three practices (discovery, formulation, automation), three amigos workshops, Gherkin scenarios, Specification by Example, living documentation, Feature Injection, and pairing BDD with outside-in TDD. Use when starting a new feature, capturing requirements collaboratively, writing acceptance criteria, deciding what scenarios to automate, or fixing a "Cucumber suite" that has become a brittle UI-testing pile.

How do I install the Behavior Driven Development skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Behavior Driven Development popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Claude Code Hooks

8

Freddy-CHEN-ux/00_claude_skills

Create event-driven hooks for Claude Code automation. Configure PreToolUse, PostToolUse, Stop, and other hook events with bash scripts, environment variables, matchers, and exit codes.

Software Development

Beam Master

8

Freddy-CHEN-ux/00_claude_skills

Shared resource library for Beam AI integration skills. DO NOT load directly - provides common references (setup, API docs, error handling, authentication) and scripts used by beam-connect and individual Beam skills.

Software Development

Claude Code Skills

8

Freddy-CHEN-ux/00_claude_skills

Comprehensive reference for creating Claude Code skills with progressive disclosure, SKILL.md structure, resources/ organization, frontmatter specification, and best practices for modular capability development.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.