bdd-scenarios

Provide the user story or feature description, select your BDD framework (Cucumber, Jest-Cucumber, or Cypress-Cucumber), and choose a detail level. The skill outputs a complete .feature file with tagged scenarios, step definitions, and a coverage matrix.

Cucumber is the standalone BDD runner, Jest-Cucumber integrates Gherkin scenarios into Jest unit test workflows, and Cypress-Cucumber pairs feature files with Cypress end-to-end tests. The skill generates step definitions tailored to whichever framework you select.

Yes. During the discovery step, the skill uses Glob and Read to examine existing feature files and step definitions in your project, then reuses established step patterns and domain language in the new scenarios.

A complete feature file covers happy path flows, edge cases, error handling, security behaviors, and performance scenarios, each tagged accordingly (for example @happy-path, @edge-case, @error, @security). The comprehensive detail level generates all of these types.

Gherkin steps should use declarative domain language describing what the system does, not how, so scenarios remain readable by non-technical stakeholders and stay stable when implementation changes. Technical jargon and UI-level mechanics make scenarios brittle and hard to maintain.