bdd

Installation
SKILL.md

Behavior-Driven Development

Use agreed business scenarios as the backbone of business acceptance. Carry the same behavior from discussion into requirement/change records, .feature, bindings, implementation, and verification evidence. Work one coherent business capability at a time; do not specify the entire project before delivering anything.

Scenarios hold the business flows and rules a stakeholder would state. Single-endpoint contracts, input validation, error enumeration, and boundary enumeration belong to lower-layer tests chosen with testing (Test Layers), not to feature files.

Ownership And Activation

Use this skill directly (/bdd in Claude Code, $bdd in Codex) or through the relevant planning, development, or acceptance workflow. Start at the stage the task needs; do not repeat completed discovery just because a new worker or skill takes over.

  • bdd owns behavior discovery, scenario formulation, and scenario-to-test correspondence.
  • The project's spec tool owns requirement intent, change decisions, and their lifecycle. OpenSpec main specs hold current intent, active changes hold deltas and decisions, and archives retain history. While a change is active, read main intent together with its delta; report pending sync/archive rather than claiming it occurred. BDD does not itself authorize archive.
  • Deterministic execution is the default for new executable BDD acceptance and existing feature-driven projects; versioned .feature files own the current branch/commit's acceptance scenarios. Keep them consistent with agreed requirements; historical artifacts do not override them. Legacy projects retain their existing convention until scoped migration, without claiming it satisfies a requested deterministic path.
  • testing, when available, owns test layers, fixtures, execution, cost, and evidence validity. Otherwise use the project's runner and testing conventions.
  • sdd, when used, tracks progress and readiness. BDD does not start a dispatch tree, gate, or progress log of its own, and does not require sdd.

For a small behavior fix, one regression scenario may be sufficient. For a pure refactor, reuse the affected scenarios and preservation tests. Do not introduce Gherkin ceremony for editorial changes or technical work with no changed business behavior. In a read-only task, report scenario or coverage gaps without editing specs or code.

Discover Before Specifying

Installs
5
Repository
noih/dev-skills
First Seen
Oct 17, 2026