scenario-design SKILL.md skillA
scenario-design from blackbelttechnology/pi-agent-dashboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add blackbelttechnology/pi-agent-dashboard/scenario-design@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- blackbelttechnology/pi-agent-dashboard
- Path
packages/eng-disciplines/.pi/skills/scenario-design/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0, committed Aug 5, 2026
- First version recorded
- Jul 13, 2026
- Size
- 12,237 bytes
- Repository stars
- 341
- License
- MIT
Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what should we test", "build a test plan", "find edge cases".
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
Turn a change spec into **adversarial, real-life test scenarios** — designed to break the system, not confirm it works. A scenario is only as good as it is *concrete and executable*. If the spec can't supply the concrete bits, that is a **spec defect**, surfaced as a clarification — not a guess. **Input**: A change/feature spec. `--change <name>` (OpenSpec), or infer from context / point the skill at any spec doc. **Mode**: `--stage proposal|design|apply` (default: infer — see Gate). **Output**: a standalone `test-plan.md` catalog written to your change/spec's test-plan location (OpenSpec: `openspec/changes/<name>/test-plan.md`). --- ## Core mechanism — the Triple Every scenario MUST resolve three concrete slots: ```text ┌─────────────┬──────────────────────┬────────────────────────────┐ │ INPUT │ TRIGGER │ EXPECTED OBSERVABLE OUTCOME │ │ concrete │ the condition / │ a measurable, visible fact │ │ data / │ action that fires │ (status, value, latency, │ │ state │ the behaviour │ DOM, log line, exit code) │ └─────────────┴──────────────────────┴────────────────────────────┘ ``` …
Read the whole file at its exact version.
How to install
mdr add blackbelttechnology/pi-agent-dashboard/scenario-design@sha256:dc18e29298f62698The line at the top of this page pins the label v1.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_4kqiqcumk5nlzjqg)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 13, 2026 and Aug 5, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-05 | ff041ae | 12,237 B | A | view · diff |
| v1.0 | 2026-07-13 | 6daa3d4 | 12,651 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 (12237 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
blackbelttechnology/pi-agent-dashboard · 341 stars · license MIT · pushed 2026-11-06 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_4kqiqcumk5nlzjqg GET https://markdownregistry.com/api/v1/resolve?ref=blackbelttechnology/pi-agent-dashboard/scenario-design GET https://markdownregistry.com/api/v1/blob/dc18e29298f6269858e7eada1115e2f2000d773d20de4baf130da47388462840
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.