create-qa-use-cases SKILL.md skillA
create-qa-use-cases from vintasoftware/vinta-ai-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vintasoftware/vinta-ai-workflows/create-qa-use-cases@git:20261003.81d5d7ePins git:20261003.81d5d7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vintasoftware/vinta-ai-workflows
- Path
skills/vinta-derive-skills/resources/foundation-skills/create-qa-use-cases/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261003.81d5d7e, committed Oct 3, 2026
- First version recorded
- May 5, 2026
- Size
- 13,380 bytes
- Repository stars
- 12
- License
- MIT
Bootstrap a project's `QA_USE_CASES.md` from scratch using the canonical pattern (immutable PA###/PR### ids, role table, per-app numbered sections with role-tagged checklists). Invoked from inside [plan-feature](../plan-feature/SKILL.md) when the project has no `QA_USE_CASES.md` yet — the active feature's spec + plan are already in hand. Seeds the file with use cases from those two documents only; does not sweep prior plans. Asks the user for the few gaps spec/plan don't answer…
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
# Bootstrap `QA_USE_CASES.md` The doc maps 1:1 to e2e test specs by an immutable id. It's the QA team's manual-test checklist and the spec filename source of truth. [add-e2e-test](../add-e2e-test/SKILL.md) appends entries; this skill creates the file the first time, **seeded from the active feature** that triggered the bootstrap. ## When to use - Project has no `QA_USE_CASES.md` at the repo root. - [plan-feature](../plan-feature/SKILL.md) is in flight for a specific feature — its spec + plan are the seed material. - A UI-flow phase in that plan needs an e2e id but the file doesn't exist yet. If `QA_USE_CASES.md` already exists, **do not overwrite**. Stop and route the user to [add-e2e-test](../add-e2e-test/SKILL.md) for appending entries. Bootstrap is one-shot. ## Source: the active feature only This skill runs **inside** the plan-feature flow, so the active spec + plan are already loaded into the conversation. Seed the file from those two documents — **do not** sweep `ai-plans/` for prior specs. Older features that pre-date this doc will be added later via [add-e2e-test](../add-e2e-test/SKILL.md) as they need test coverage; bootstrapping with the entire history is noise. …
Read the whole file at its exact version.
How to install
mdr add vintasoftware/vinta-ai-workflows/create-qa-use-cases@sha256:6cbcccb58411e693The line at the top of this page pins the label git:20261003.81d5d7e, 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_bvioara6cyiizicf)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 5, 2026 and Oct 3, 2026, about one every 50 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.81d5d7e latest | 2026-10-03 | 81d5d7e | 13,380 B | A | view · diff |
| git:20260529.0f36bde | 2026-05-29 | 0f36bde | 13,126 B | A | view · diff |
| git:20260513.f57f3c6 | 2026-05-13 | f57f3c6 | 12,852 B | A | view · diff |
| git:20260505.319f26e | 2026-05-05 | 319f26e | 12,853 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 (13380 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
vintasoftware/vinta-ai-workflows · 12 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bvioara6cyiizicf GET https://markdownregistry.com/api/v1/resolve?ref=vintasoftware/vinta-ai-workflows/create-qa-use-cases GET https://markdownregistry.com/api/v1/blob/6cbcccb58411e6934491a66b42f117b77923ff62e46eff003b86054f4f40bac8
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.