bdd-scenario-writer SKILL.md skillA
bdd-scenario-writer from pramoddutta/aitesterblueprint4x is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pramoddutta/aitesterblueprint4x/bdd-scenario-writer@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pramoddutta/aitesterblueprint4x
- Path
chapter_14_MCP_Create_VIBE/testskill-finder-mcp/skills/03-test-design/bdd-scenario-writer/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 10, 2026
- Size
- 3,389 bytes
- Repository stars
- 14
- License
- none declared
Write Gherkin feature files (Feature, Background, Scenario Outline with Examples, tags) from acceptance criteria, using declarative business-language steps. Use when a tester or SDET says "write BDD scenarios for this story", "convert these ACs to Gherkin", "create a feature file", or pastes acceptance criteria. Produces a tagged .feature draft traced to each AC, and stops for human review before it is automated.
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
# BDD Scenario Writer You write **feature files a product owner can read and an SDET can automate** without rewriting. Steps describe behavior in business language, never clicks and selectors. ## When to use - Approved acceptance criteria need to become executable specifications. - An existing feature file is full of imperative "click the button" steps and needs a rewrite. - A Three Amigos session produced examples that should be captured as Gherkin. ## Workflow 1. **Collect ACs and vocabulary.** Ask for the acceptance criteria, domain terms, personas and any existing step library. If an AC is missing an outcome, ask; do not invent one. 2. **Map ACs to scenarios.** At least one scenario per AC, tagged with its AC ID. Add a negative scenario where the AC implies a rejection path. 3. **Extract a Background only when it is true for every scenario.** Keep it to a few Given lines; anything scenario-specific stays in the scenario. 4. **Use Scenario Outline when only data varies.** Put variations in Examples with column names that explain meaning. Different outcomes deserve separate outlines. …
Read the whole file at its exact version.
How to install
mdr add pramoddutta/aitesterblueprint4x/bdd-scenario-writer@sha256:80ea2e38fb54f431The line at the top of this page pins the label v1.0.0, 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_ldktlfa2d4xz5kpg)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
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 (3389 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
pramoddutta/aitesterblueprint4x · 14 stars · license none declared · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ldktlfa2d4xz5kpg GET https://markdownregistry.com/api/v1/resolve?ref=pramoddutta/aitesterblueprint4x/bdd-scenario-writer GET https://markdownregistry.com/api/v1/blob/80ea2e38fb54f431950610fd503a903980ff0bec276b44b3ec1f53264add908a
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.