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 empowers software teams to implement high-quality Behavior Driven Development (BDD) practices. It guides the creation of intent-based test scenarios that focus on business value and observable outcomes, ensuring that tests remain robust, readable, and decoupled from fragile UI implementation details. By enforcing the use of business language and service-level mapping, it bridges the gap between technical requirements and stakeholder expectations.
Use Cases
- Scenario Authoring: Draft clear, business-focused Gherkin examples that align with stakeholder requirements and domain glossaries.
- Test Refactoring: Convert brittle, UI-heavy test scripts into maintainable, service-oriented BDD steps to reduce test suite flakiness.
- Technical Alignment: Map high-level user intents directly to backend application services, facilitating better communication between developers and QA teams.
- BDD Mentorship: Provide real-time feedback and guidance to engineers on writing effective, observable test outcomes rather than mechanical UI steps.
| 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.