gherkin-from-stories SKILL.md skillA
gherkin-from-stories from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/gherkin-from-stories@git:20260813.83125c6Pins git:20260813.83125c6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-bdd/skills/gherkin-from-stories/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260813.83125c6, committed Aug 13, 2026
- First version recorded
- Jul 6, 2026
- Size
- 12,927 bytes
- Repository stars
- 11
- License
- MIT
Converts requirements in any input shape into Gherkin scenarios - a user story ("As a … I want … so that …"), a signed-off acceptance-criteria list (ATDD: @AC-N-tagged scenarios, NotImplementedError step stubs, AC-to-test traceability table), existing manual test steps (declarative rewrite that strips UI mechanics), or a raw spec / PRD section (acceptance-criteria extraction with Gherkin or plain-list output). Maps criteria to Scenario blocks, detects Scenario Outline opportunities, factors…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add testland/qa/gherkin-from-stories@sha256:ec014aa78447ff5bThe line at the top of this page pins the label git:20260813.83125c6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_55i3lcu3chpjrcwl)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 6, 2026 and Aug 13, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260813.83125c6 latest | 2026-08-13 | 83125c6 | 12,927 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 8,203 B | A | view · diff |
| git:20260719.53f73b7 | 2026-07-19 | 53f73b7 | 8,368 B | A | view · diff |
| git:20260718.ab29907 | 2026-07-18 | ab29907 | 8,215 B | A | view · diff |
| git:20260706.d9cec5f | 2026-07-06 | d9cec5f | 8,546 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12927 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_55i3lcu3chpjrcwl GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/gherkin-from-stories GET https://markdownregistry.com/api/v1/blob/ec014aa78447ff5b3c61c0992ab9890ce300d663020eca46de81c793a1c3a629
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.