Skip to main content
skill CX Codex

behavior-driven-development — Claude Code skill

behavior-driven-development — a BDD skill for feature work, bug fixes, and executable tests. It turns behavior examples into failing tests before implementation.

MIT 151 installs ★ 597 updated 2026-10-09

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add FradSer/dotclaude --skill behavior-driven-development -a claude-code
Open on GitHub

What behavior-driven-development does

This skill guides coding tasks through behavior examples written as Gherkin scenarios. The flow starts with clarifying requirements, moves to Given/When/Then examples, and uses Red-Green-Refactor to drive the implementation.

Keep planning scenarios in bdd-specs.md; move scenarios chosen for automation into .feature files or the test framework’s executable format. The skill also points to ./references/bdd-best-practices.md, ./references/gherkin-guide.md, and ./references/testing-anti-patterns.md.

Production code must follow a failing test. Run that test and confirm the failure has the intended cause before implementing anything. Existing implementation is removed and rebuilt from the test, with exceptions described in ./references/bdd-best-practices.md.

What it helps with

  • turn feature behavior into Gherkin scenarios
  • verify a bug fix with a failing test
  • separate planning specs from executable tests
  • drive implementation through Red-Green-Refactor

Example prompts for the agent

  • Describe this feature with Given/When/Then scenarios, then write a test that fails for the expected reason.
  • Fix the bug test-first and inspect the failure before changing production code.
  • Move the reviewed scenarios from bdd-specs.md into .feature files and implement them with TDD.

How to install behavior-driven-development

1Skills CLI (Vercel)

npx skills add FradSer/dotclaude --skill behavior-driven-development -a claude-code

2Manually: put the files in place

~/.claude/skills/behavior-driven-development/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/behavior-driven-development/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about behavior-driven-development

How do I install behavior-driven-development in Claude Code?

Run npx skills add FradSer/dotclaude --skill behavior-driven-development -a claude-code. The skill is placed at ~/.claude/skills/behavior-driven-development/SKILL.md.

What does behavior-driven-development do?

It takes a task from behavior examples and Gherkin scenarios to a failing test, minimal implementation, and refactoring.

Where should BDD scenarios be stored?

Use bdd-specs.md for planning. Put scenarios selected for automation in .feature files or the executable format supported by the test framework.

Source text

SKILL.md · MIT
---
name: behavior-driven-development
description: Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
user-invocable: false
---

# Behavior-Driven Development (BDD) Skill

This skill provides a comprehensive guide to applying Behavior-Driven Development principles to your coding tasks. BDD is not just about tools; it's a methodology for shared understanding and high-quality implementation.

## How to Use This Skill

When the user asks for a feature, bug fix, or refactor, apply the following mindset:

1.  **Understand Behavior First:** Do not start coding until you know *what* the system should do.
2.  **Define Scenarios:** Create or ask for concrete examples (Gherkin) of the expected behavior.
3.  **Drive Implementation with Tests:** Use the Red-Green-Refactor cycle.

## Core Concepts

### 1. The BDD Cycle
The process flows from requirements to code:
*   **Discovery:** Clarify requirements through examples (The "Three Amigos").
*   **Formulation:** Write these examples as specific scenarios (Given/When/Then).
*   **Automation:** Implement using TDD.

See `./references/bdd-best-practices.md` for a detailed guide.

### 2. Writing Scenarios (Gherkin)
Scenarios are your "Executable Specifications".
*   Keep them declarative (business focus).
*   Avoid technical jargon and UI details.
*   One behavior per scenario.
*   Use `bdd-specs.md` as the planning-stage scenario inventory in the superpowers workflow. During brainstorming and plan writing, keep the reviewed Given/When/Then scenarios in `docs/plans/.../bdd-specs.md` so design review, task decomposition, and sprint contracts all read from the same source.
*   **Store executable scenarios in .feature files, NOT as code comments** - once implementation begins, translate the scenarios that will be automated into `.feature` files or the framework-native executable test format. `bdd-specs.md` is for design and planning; `.feature` files are for automation and living documentation.

See `./references/gherkin-guide.md` for syntax and storage structure.

### 3. Red-Green-Refactor (TDD)
The engine of implementation:
1.  **RED:** Write a failing test for the scenario (or a unit thereof).
2.  **GREEN:** Write the minimal code to pass the test.
3.  **REFACTOR:** Clean up the code while keeping tests passing.

## CRITICAL: The Iron Law

> **"No production code is written without a failing test first."**

The Red step MUST verify the test fails for the right reason (run the test and read the failure output) before writing any implementation. Skipping or rationalizing this step produces:

1.  Tests that pass spuriously — you cannot tell if they are capable of failing.
2.  Implementation-biased tests — they reflect the code that was written, not the behavior under contract.
3.  Legacy code from day one — no behavioral safety net catches future regressions.

### If Production Code Already Exists

Delete it and re-derive it from a failing test — do not keep it "as reference," do not "adapt" it into the test-first version, do not read it while writing the test. Any of those re-introduces the implementation-biased-test failure mode above through the back door: a test written while looking at the code it's meant to constrain will pass on the first try regardless of whether it checks the right thing. Delete means delete.

### Common Rationalizations (reject all of these)

| Rationalization | Why it fails |
|---|---|
| "I'll write the test after — same coverage either way" | A test written against working code always passes on the first run. That proves the test doesn't crash, not that it verifies the right behavior. Only a test that failed first, for the stated reason, has been shown capable of catching a regression. |
| "I already manually verified it works" | Manual verification is not repeatable and leaves no regression guard. It answers "did this work once," not "will this keep working." |
| "This is too simple to need a test" | Simple code changes behavior just as easily as complex code. The Iron Law has no complexity threshold — it has the three named exceptions below and nothing else. |
| "I'll be pragmatic, not dogmatic, about TDD" | This is the rationalization, not an alternative to it. Every one of these tables' entries is someone being "pragmatic" about skipping the Red step. |
| "I already spent an hour on this, deleting it is wasteful" | Sunk cost. The hour is already spent whether you delete the code or keep it; keeping untested code doesn't recover that hour, it just adds an unverified regression risk on top of it. |

The only legitimate exceptions are named in `./references/bdd-best-practices.md` (one-off prototypes, generated code, config files) — and even those should be raised with the user, not silently assumed.

### Tests Written After the Fact Answer a Different Question

A test-first test encodes "this is what the system is contracted to do." A test-after test encodes "this is what the code I already wrote happens to do" — it will pass even if the code has the wrong behavior, because it was shaped to match that behavior rather than an independent specification. If you catch yourself writing a test against code you can already see, stop, delete the code, and write the test against the *behavior* instead.

## References

- `./references/bdd-best-practices.md` - BDD methodology, discovery, formulation, and automation
- `./references/gherkin-guide.md` - Gherkin scenario syntax, storage structure, and examples
- `./references/testing-anti-patterns.md` - Mocking pitfalls and other ways tests can pass without verifying real behavior

© FradSer · MIT · FradSer/dotclaude

Similar skills

All skills for Testing and QA →
test-driven-development Jesse Vincent The test-driven-development skill guides an agent through test-first development: verify a test fails, write the smallest passing change, then refactor. It covers features, bug fixes, and behavior changes. CX Codex +1 259,292installs backend-development-test-automator Seth Hobson backend-development-test-automator — a subagent for generating unit, integration, and E2E test suites during feature development. Works with your existing frameworks and supports TDD and BDD. CX Codex ★ 42,780repo stars bdd-patterns TheBushidoCollective bdd-patterns helps agents write BDD specifications with Given–When–Then, feature files, and acceptance criteria. Use it when behavior must guide implementation. CX Codex +1 211installs bdd-scenarios TheBushidoCollective This skill helps turn requirements into BDD scenarios, acceptance criteria, and edge cases. Use it to clarify expected behavior before implementation. CX Codex +1 180installs gherkin-style-testing-cursorrules-prompt-file PatrickJS gherkin-style-testing-cursorrules-prompt-file — a Cursor rule that turns technical test scripts and manual cases into Gherkin scenarios written in plain business language. CX Codex +1 ★ 41,178repo stars principle-test-behavior-not-implementation backnotprop principle-test-behavior-not-implementation is a Claude Code skill that guides testing public behavior over internals. It activates whenever tests are authored, modified, or reviewed. CX Codex +1 10,200installs

From the same set16

The whole set →
patent-architect patent-architect searches prior art through SerpAPI or WebSearch and drafts Chinese patent application forms. Handy when documenting technical innovations. CX Codex +1 622installs executing-plans executing-plans — a skill for Claude Code, Codex, and Cursor. Executes written implementation plans in task batches using isolated coordinator sub-agents and a single final commit. CX Codex +1 126installs commit-and-push commit-and-push — a skill for Claude Code, Codex, Cursor, and other platforms that generates atomic commits using Conventional Commits standard via git-agent and pushes them to the remote repository. CX Codex +1 126installs brainstorming brainstorming — a skill for Claude Code and five other tools that turns raw ideas into ready BDD specs. It researches your codebase autonomously and commits the technical design without asking questions mid-run. CX Codex +1 124installs writing-plans writing-plans — a skill for Claude Code, Codex, Cursor and other platforms that transforms a finished design into an executable implementation plan. CX Codex +1 123installs refactor-project refactor-project — a skill for Claude Code, Codex, Cursor and other agents that runs automated refactoring across every file in the project at once. Cuts duplication, normalises patterns, and strips legacy code in a single pass. CX Codex +1 122installs plugin-best-practices plugin-best-practices validates Claude Code plugin structure, manifests, and architecture against framework standards. Ensures your plugin meets requirements before marketplace submission. CX Codex +1 121installs commit This skill creates atomic conventional commits through git-agent. Use it when a short intent should become a focused Git commit. CX Codex +1 121installs

Project sponsors

Companies that keep this analytics open