bdd-guidelisted
Install: claude install-skill xonovex/platform
# Behaviour- and Acceptance-Driven Development
Drive software from concrete, agreed examples of behaviour. Discover them in conversation, formulate them as Given-When-Then scenarios, and keep the executable scenarios as living documentation. The acceptance layer answers "are we building the right thing?" The inner domain logic is still driven test-first by **tdd-guide**. ATDD and BDD are two names for this one practice.
## Essentials
- **Discover before you formulate** - run a three-amigos conversation over real examples first, see [references/discovery-three-amigos.md](references/discovery-three-amigos.md)
- **Map examples to size and split the story** - yellow/blue/green/red cards expose scope and gaps, see [references/discovery-three-amigos.md](references/discovery-three-amigos.md)
- **Write scenarios in Gherkin Given-When-Then** - Feature, Scenario, Background, Outline; declarative steps, see [references/gherkin-reference.md](references/gherkin-reference.md)
- **Treat scenarios as living documentation** - specs and tests become one trustworthy artefact, see [references/specification-by-example.md](references/specification-by-example.md)
## Gotchas
- Gherkin/Cucumber is a **collaboration** tool that tests the team's shared UNDERSTANDING of unwritten software, not a testing tool: automation is the third practice, never the purpose, see [references/appendix-discovery.md](references/appendix-discovery.md).
- "Three amigos" means three PERSPECTIVES (business / development