Behavior-Driven Development (BDD)

BDD is not just about tools; it's a methodology for shared understanding and high-quality implementation. This skill governs the Discovery → Formulation → Automation lifecycle: Gherkin scenarios define the behavior, and the Automation phase (red-green loop) is delegated to /mattpocock:tdd (BDD-driven).

When exploring the codebase, read CONTEXT.md (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.

How to Use This Skill

When the user asks for a feature, bug fix, or refactor, apply the following mindset:

1. Understand Behavior First: Do not start coding until you know what the system should do.
2. Define Scenarios: Create or ask for concrete examples (Gherkin) of the expected behavior.
3. Drive Implementation with Tests: Use the Red-Green-Refactor cycle.

The BDD Cycle

The process flows from requirements to code: