test-scenario-designer SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
test-scenario-designer 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/test-scenario-designer@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/test-scenario-designer/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 10, 2026
- Size
- 2,963 bytes
- Repository stars
- 14
- License
- none declared
Derive high-level test scenarios from a requirement or acceptance criteria before anyone writes detailed steps. Use when a tester says "what scenarios should we test", "design scenarios for this feature", or pastes ACs and wants coverage mapped out. Produces positive, negative, boundary, and cross-role scenarios, each tagged by risk and traced back to the AC it exercises, then stops for review before test cases are written.
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
# Test Scenario Designer You turn requirements into a **coverage map** — the set of things worth testing — one level above step-by-step cases. Breadth and traceability matter more than detail here. ## When to use - ACs or a feature description exist and you need the "what could go right/wrong" list. - You want coverage agreed and reviewed before investing in detailed test cases. - A reviewer asks "did we think about the negative and boundary paths?" ## Workflow 1. **Read the source.** Take the requirement, ACs, or analyzer output. If it is too vague to derive scenarios, say so and route back to requirement analysis — do not guess intent. 2. **Enumerate by category.** For each AC, generate scenarios across: positive (happy path), negative (invalid input, errors, permissions denied), boundary (empty, min, max, limits), and cross-role / cross-state (different personas, concurrent or interrupted flows). 3. **Tag risk.** Mark each scenario P0/P1/P2 by likelihood × impact. Note non-functional angles (perf, security, a11y, i18n) where relevant. 4. **Trace.** Map every scenario to the AC or gap it covers; flag ACs with zero scenarios …
Read the whole file at its exact version.
How to install
mdr add pramoddutta/aitesterblueprint4x/test-scenario-designer@sha256:ed1522b76535f77dThe 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_neqwmvu4otpaqkab)
2 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 (2963 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_neqwmvu4otpaqkab GET https://markdownregistry.com/api/v1/resolve?ref=pramoddutta/aitesterblueprint4x/test-scenario-designer GET https://markdownregistry.com/api/v1/blob/ed1522b76535f77da851866184781ceb0fadb3f1271603ec59d42b22615a880b
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.
More from pramoddutta/aitesterblueprint4x
Every file in pramoddutta/aitesterblueprint4x