What problem does it solve? Poorly written Gherkin feature files — imperative steps, bundled behaviors, brittle hardcoded data — produce flaky, hard-to-maintain test suites that stakeholders stop reading. This Skill provides the conventions needed to keep .feature files readable as living documentation while remaining cheap to maintain as implementations change. ## Core Features & Use Cases - Feature structure guidance: Rules for feature titles, Connextra/inverted narratives, one-feature-per-file scoping, and disciplined Background usage. - Step writing standards: Given-When-Then integrity, declarative over imperative phrasing, third-person present tense, and atomic single-behavior scenarios. - Scenario Outlines and data: Guidance on Examples tables, inline data tables, and Doc Strings for data-driven scenarios. - Review checklists: A consolidated anti-patterns reference with before/after examples for auditing existing feature files. - Use Case: Convert a set of acceptance criteria from a ticket into a well-structured .feature file with a narrative, Background, and scenarios covering both happy and unhappy paths. ## Quick Start Write a Gherkin feature file for the user login requirement, using declarative steps, a Background for shared state, and scenarios for both successful and failed login attempts.