← ClaudeAtlas

gherkin-from-storieslisted

Use whenever user stories, acceptance criteria, manual test steps or a spec need to become Gherkin, or when asked how to write good acceptance scenarios: maps each criterion to scenarios, finds Scenario Outlines and Background, reuses existing steps and flags hidden preconditions. Writes .feature files only, not step code.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# gherkin-from-stories ## Overview The shift-left flow: ``` Spec / User story → Acceptance Criteria → Gherkin Feature → Step definitions → Tests ``` This skill is the authoring umbrella for the left half of that flow: it turns requirements text into a `.feature` file. Four input shapes route to the same core transform: | Input you have | Section to use | Extra output | |---|---|---| | A user story with the As-a / I-want / So-that triple | "From a user story" | - | | A signed-off, numbered acceptance-criteria list | "From an acceptance-criteria list (ATDD)" | `@AC-N` tags, step stubs, traceability table | | Already-written manual test steps (TestRail / Qase / Xray export, prose script) | "From manual test steps" | side-by-side rewrite table | | A raw spec / PRD section with no AC structure yet | "Extracting acceptance criteria from a raw spec" | Gherkin or plain numbered AC list | Whatever the input, the same core discipline applies: one Scenario per behavior, Scenario Outline when only data varies, shared Background, step library reuse, and flag-and-ask on implicit preconditions. ## When to use - A PM hands over a story, spec, or AC list and the team's first test artifact is the `.feature` file. - The team practices ATDD and gates stories on green acceptance tests. - A team is migrating manual test scripts (or a whole TestRail / Qase library) to BDD. - A migration from non-BDD to BDD wants to convert existing requirements into Gherkin in bulk. Not this skill: r