BDD and ATDD

Purpose

Drive development through shared examples and executable specifications using Behavior-Driven Development and Acceptance Test-Driven Development. Ensures shared understanding across business and technical stakeholders, produces living documentation that stays in sync with the code, and enables automated validation of business rules.

Agent Protocol

Trigger

"BDD", "ATDD", "behavior-driven development", "acceptance test-driven development", "Gherkin", "Cucumber", "SpecFlow", "specification by example", "executable specification", "living documentation", "three amigos", "example mapping", "acceptance criteria", "scenario", "feature file", "step definition".

Input Context

• Feature or user story to be implemented
• Business rules and acceptance criteria (existing or to be defined)
• Technical stack: programming language, test framework, BDD tool
• Key examples of expected behavior (inputs, outputs, edge cases)
• Stakeholders available for three amigos session
• Existing test infrastructure (CI pipeline, reporting)