qa-bdd

Action-taking agent that authors Gherkin scenarios and scaffolds step definitions end-to-end - accepts a user story or acceptance criteria list, invokes gherkin-from-stories or acceptance-test-from-criteria to produce a Feature file, detects the project's BDD runner (Cucumber-JVM, Cucumber-JS, Cucumber-Ruby, Behave, Reqnroll, or SpecFlow), and emits idiomatic step definition stubs wired to that runner. De-duplicates against the existing step library via bdd-step-library-curator before adding new steps. Fills the build counterpart to gherkin-style-reviewer: that agent critiques; this one authors. Use when a story or AC list needs to be turned into runnable BDD tests.

Adversarial reviewer for Gherkin Feature files - flags imperative steps ("click button #foo"), technical leakage (DB names / API URLs / CSS selectors in steps), "And And And" chains (excessive coordination), missing Background extraction (repeated Givens across scenarios), and Then-without-observable-outcome (vague assertions). Refuses to mark a Feature "good" if any flag remains. Use during PR review against `*.feature` files.

Configures Reqnroll (the canonical .NET BDD framework) - install via `dotnet add package Reqnroll`, author `.feature` files in Gherkin, write step bindings as `[Given/When/Then]`-decorated methods in any C# class, runs via `dotnet test`. Reqnroll is the SpecFlow successor (originated as a community port off the SpecFlow codebase); new .NET BDD work targets Reqnroll. Use for .NET projects starting BDD or migrating from SpecFlow.

Legacy support for SpecFlow (.NET BDD framework that predates Reqnroll) - for projects that haven't migrated yet. Mirrors Reqnroll's API closely (Reqnroll is the SpecFlow fork). Body documents the SpecFlow patterns + the migration path to Reqnroll. Per Reqnroll's own positioning, new .NET BDD work targets Reqnroll, not SpecFlow. Use only for existing SpecFlow projects mid-migration; new projects use `reqnroll-testing` instead.

Build-an-X workflow for ATDD (Acceptance Test-Driven Development) - converts acceptance criteria into executable acceptance tests in the team's BDD framework (Cucumber / Behave / Reqnroll), pairs with the relevant runner, scaffolds step definitions for new patterns, marks generated tests as "AC-N" so failures map back to the story's acceptance criterion. Use when the team practices ATDD and wants automation generated from ACs as a first-class step before development.

Build-an-X workflow that keeps step definitions DRY across a Cucumber / Behave / Reqnroll project - periodically inventories step definitions, finds duplicates (different patterns matching the same intent), suggests consolidation, organizes by domain, and publishes a step library reference doc the team uses for "is there already a step for X?" before authoring new ones. Use as the antidote to step-definition proliferation in long-lived BDD projects.

Configures Behave for Python BDD scenarios - `pip install behave`, authors `.feature` files in Gherkin, writes step implementations in `features/steps/*.py`, configures via `environment.py` for setup/teardown hooks, organizes via tags, runs via `behave`. Use for Python codebases that want Cucumber-family BDD without Cucumber-Ruby / Cucumber-JS.