BDD Methodology

BDD Methodology is a Quality skill for Claude Code, published by nWave-ai in nWave.

598 stars61 forkson nWave-ai/nWaveAdded 2026/08/25+1% in starsRepository updated 2026/06/27

agentic-aiagentic-codingagentic-frameworkagentic-workflowaiatddbddclaude-codeclaude-code-cliclaude-code-commandsclaude-code-hooksclaude-code-skillsclaude-code-subagentsdevopslean-uxopencodesoftware-architecturesoftware-craftmanshiptdd

Install in seconds

Install BDD Methodology

Copy BDD Methodology into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-bdd-methodology ~/.claude/skills/nw-bdd-methodology

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/nWave-ai/nWave.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: nWave/skills/nw-bdd-methodology/SKILL.md in nWave-ai/nWave
Installs to: ~/.claude/skills/nw-bdd-methodology
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What BDD Methodology does

BDD Methodology defines acceptance test design with Given-When-Then scenarios, scenario-writing rules, and pytest-bdd implementation. Use it to write living documentation and avoid common BDD anti-patterns.

BDD Methodology is cataloged under Quality on DirSkills. BDD Methodology comes from a repository tagged agentic-ai, agentic-coding, agentic-framework, agentic-workflow and ai.

Documentation

README

Excerpt

BDD Methodology for Acceptance Test Design

Core Philosophy

Test units of behavior, not units of code. Acceptance tests validate business outcomes through public interfaces, decoupled from implementation.

Outside-In Double-Loop TDD

The acceptance-designer creates the outer loop of Outside-In TDD. Development starts from user perspective, drives inward.

Outer loop (acceptance/BDD): Hours to days | User perspective, business language | Defines "done" | Scenarios describe user goals and observable outcomes, not internals | Failing outer-loop test is the starting signal for implementation

Inner loop (unit/TDD): Minutes | Developer perspective, technical terms | Software-crafter owns this loop

This is the opening of the README. Read the full README on GitHub.

Frequently asked about BDD Methodology

What else does nWave-ai publish alongside BDD Methodology?
BDD Methodology is one of 25 skills that DirSkills catalogs from nWave-ai/nWave, the repository it ships in. Its siblings there include AT Completeness Check, Acceptance Test Critique Dimensions and Agent Creation Workflow. Each one is a separate skill with its own page in this directory, installs the same way BDD Methodology does, and is maintained by nWave-ai in that same repository. The rest of the collection is listed on the nWave-ai/nWave page.
How does BDD Methodology compare to other Quality skills?
BDD Methodology ranks #1131 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of BDD Methodology against them. Open each page to compare what they document and how they install.