What problem does it solve? Turning tickets, user stories, or plain-prose requirements into clear, executable Gherkin specifications is hard: scenarios often leak UI or API mechanics, mix multiple behaviors, or assert vague outcomes. This Skill guides the authoring of domain-level .feature files that read as specification by example and survive as living documentation. ## Core Features & Use Cases - Discovery-driven formulation: Maps a work item into rules, examples, and open questions using Example Mapping, and asks clarifying questions instead of guessing requirements. - Domain-level scenario writing: Enforces one behavior per scenario, Given/When/Then mapped to Arrange/Act/Assert, observable outcomes, and concrete realistic data, while stripping selectors, URLs, waits, and SQL from step text. - Structure guidance: Applies Background, Scenario Outline, and data tables only when they earn it, and keeps one shared vocabulary across the feature file. - Use Case: Given a ticket describing discount codes at checkout, produce a discount-codes.feature file with separate scenarios for valid and unknown codes, each with concrete amounts and observable outcomes. ## Quick Start Ask the assistant to turn this user story into Gherkin scenarios for a feature file, keeping steps at the domain level with one behavior per scenario.
