skill
behavior-driven-development
Apply Behavior-Driven Development to clarify user-visible behavior, acceptance criteria, business workflows, and executable examples before or during implementation. Do not use to author formal .feature syntax; use gherkin.
Description as published by the maintainer. Source
- active
active — Most recent push to the repository was 2026-08-01.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Stars on the repository that contains this skill, not on the skill itself. A collection of fifty skills shares one number, so it says nothing about this particular skill. | cumulative, all time | GitHub | |
| Last commit | 2026-08-01 | Most recent push to the containing repository. It may reflect work on a different skill in the same collection. | point in time | GitHub | |
| repository status | active | The repository holding this skill exists and is not archived. | as of fetch | GitHub |
Will this work with your setup?
No harness stated by the author and no install path convention detected. Compatibility is untested.
We have not run this skill against a task with and without it enabled, so we cannot tell you whether it improves anything, what it costs in tokens, or whether it duplicates behaviour your harness already has. When we have run that test, the result will appear on this page with the task, the versions and the budget it used.
The skill definition lives at skills/behavior-driven-development/SKILL.md in https://github.com/nledford/engineering-review-board.
Where to get it
Also from nledford
-
nledford-engineering-review-board-adversarial-review
— last commit 2026-08-01
Skeptically verify completed changes, agent work, merge readiness, and hidden regressions. Use after implementation whe…
-
nledford-engineering-review-board-architecture-review
— last commit 2026-08-01
Review architectural boundaries, dependency direction, ports and adapters, Clean/Onion/Hexagonal/DDD hybrids, and modul…
-
nledford-engineering-review-board-brainstorming
— last commit 2026-08-01
Structured ideation for ambiguous software engineering work. Use when agents need to generate multiple options, compare…
-
nledford-engineering-review-board-ci-release-engineering
— last commit 2026-08-01
Implement, change, review, or test checked-in CI and release provider configuration, including workflow triggers, job g…
-
nledford-engineering-review-board-clean-architecture
— last commit 2026-08-01
Clean Architecture guidance centered on the dependency rule, entities, use cases/interactors, and interface adapters th…
-
nledford-engineering-review-board-code-review
— last commit 2026-08-01
Perform repository-local code reviews. Use for requested diff or pull-request audits, final focused review after implem…
-
nledford-engineering-review-board-container-engineering
— last commit 2026-08-01
Implement, change, review, or test Dockerfile, Containerfile, .dockerignore, BuildKit/OCI image, and Docker Compose con…
-
nledford-engineering-review-board-create-agent-skill
— last commit 2026-08-01
Create or improve reusable agent skills. Use when the user asks to create a new skill, update an existing skill, define…
-
nledford-engineering-review-board-csharp-dotnet-engineering
— last commit 2026-08-01
C# and .NET engineering guidance. Use when adding, changing, reviewing, testing, packaging, restoring, building, publis…
-
nledford-engineering-review-board-css-scss-styling
— last commit 2026-08-01
CSS, SCSS/Sass, and Tailwind CSS styling guidance. Use when adding, changing, reviewing, refactoring, adopting, or migr…
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab