What problem does it solve? Teams struggle to bridge the gap between business requirements and executable tests, leading to miscommunication between technical and non-technical stakeholders. This Skill provides structured guidance for writing behavior-driven development specifications that serve as both documentation and automated tests. ## Core Features & Use Cases - Gherkin Syntax Reference: Complete coverage of Feature, Scenario, Given/When/Then, Background, Scenario Outline, Data Tables, Doc Strings, Tags, and Rule keywords. - Step Definition Patterns: Ready-to-use examples for Cucumber.js (JavaScript), pytest-bdd (Python), and Cucumber-JVM (Java), including hooks, fixtures, and state sharing. - Tool Selection Guidance: Comparison of Cucumber.js, pytest-bdd, Behave, SpecFlow, Karate, and RSpec with selection flowcharts by language and use case. - Use Case: A QA engineer needs to automate acceptance tests for a shopping cart feature. Use this Skill to write a Gherkin feature file with scenario outlines for discount codes, then implement matching step definitions in pytest-bdd. ## Quick Start Ask the AI to write a Gherkin feature file with scenarios and step definitions for user login using Cucumber.js.