| name | 058-design-bdd |
| description | Use when a Java change needs independent Behavior-Driven Development guidance from trusted behavior facts through concrete examples and observable scenarios, with focused clarification when behavior is pending or ambiguous. This should trigger for requests such as Apply BDD; Facilitate behavior examples; Discover scenarios with Given When Then; Review these examples for shared domain language; Complete BDD discovery as a self-contained interaction. Part of Plinth Toolkit |
| license | Apache-2.0 |
| metadata | {"author":"Juan Antonio Breña Moral","version":"0.18.0"} |
Behavior-Driven Development Design
Guide Java Enterprise teams through Behavior-Driven Development as a collaborative discovery and design practice. This is an interactive SKILL.
What is covered in this Skill?
- Establishing maintainer-provided or maintainer-sanitized behavior facts, actors, outcomes, rules, and terminology
- Discovering concrete main, alternative, boundary, and error examples without inventing unsupported behavior
- Formulating observable scenarios in shared domain language with Given/When/Then where useful
- Using the bundled
references/058-design-bdd.md as the complete Gherkin syntax reference
- Producing a self-contained BDD outcome that can be reused in a later, separately requested interaction
- Reporting conflicts, unresolved decisions, deferred examples, and remaining risks
Constraints
Keep BDD grounded in trusted facts, collaborative discovery, shared language, and externally observable behavior.
