bdd-playbook
Guides BDD example-writing: intent-based steps, observable outcomes, and mapping steps to services.
When & Why to Use This Skill
The BDD Playbook skill is designed to streamline Behavior-Driven Development by guiding users through the creation of high-quality, intent-based test scenarios. It emphasizes business-centric language and observable outcomes over brittle UI mechanics, ensuring that software requirements are clearly defined, easily testable, and perfectly aligned with application services.
Use Cases
- Scenario Authoring: Drafting Gherkin-style examples that focus on business value and user intent rather than technical implementation details.
- Test Refactoring: Converting legacy, UI-dependent test scripts into robust, service-mapped BDD scenarios to reduce maintenance overhead.
- Stakeholder Alignment: Using the built-in glossary and business language guidelines to bridge the communication gap between product owners and developers.
- QA Training: Serving as an interactive guide for junior engineers to learn BDD best practices and how to avoid common pitfalls like 'click-and-type' scripting.
| name | bdd-playbook |
|---|---|
| description | Guides BDD example-writing: intent-based steps, observable outcomes, and mapping steps to services. |
| allowed-tools | Read, Edit, Grep, Glob |
BDD Playbook (training)
- Scenarios read like real examples.
- Use business language from the glossary.
- Outcomes are observable.
- Avoid UI mechanics (click/type/wait). Map steps to application services, not UI clicks.