qa-plan 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.
qa-plan from striderza/opencodegamestudios is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add striderza/opencodegamestudios/qa-plan@git:20260622.695134dPins git:20260622.695134d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- striderza/opencodegamestudios
- Path
.agents/modules/qa/skills/qa-plan/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260622.695134d, committed Jun 22, 2026
- First version recorded
- Jun 21, 2026
- Size
- 11,143 bytes
- Repository stars
- 99
- License
- MIT
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.
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
# QA Plan This skill generates a structured QA plan for a sprint, feature, or individual story. It reads all in-scope story files and their referenced GDDs, classifies each story by test type, and produces a plan that tells developers exactly what to automate, what to verify manually, what the smoke test scope is, and when to bring in a playtester. Run this before a sprint begins so the team knows upfront what testing work is required. A test plan written after implementation is a post-mortem, not a plan. **Output:** `production/qa/qa-plan-[sprint-slug]-[date].md` --- ## Phase 1: Parse Scope **Argument:** `$ARGUMENTS` (blank = ask user via question) Determine scope from the argument: - **`sprint`** — read the most recent file in `production/sprints/`, extract every story file path referenced. If `production/sprint-status.yaml` exists, use it as the primary story list and fall back to the sprint plan for story metadata. - **`feature: [system-name]`** — glob `production/epics/*/story-*.md`, filter to stories whose file path or title contains the system name. Also check the epic index file (`EPIC.md`) in that system's directory. …
Read the whole file at its exact version.
How to install
mdr add striderza/opencodegamestudios/qa-plan@sha256:fea238b6e8e3bd24The line at the top of this page pins the label git:20260622.695134d, 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_gai7gvr3zcbk7iqm)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 21, 2026 and Jun 22, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260622.695134d latest | 2026-06-22 | 695134d | 11,143 B | A | view · diff |
| git:20260621.096f040 | 2026-06-21 | 096f040 | 11,143 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 (11143 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
striderza/opencodegamestudios · 99 stars · license MIT · pushed 2026-10-06 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_gai7gvr3zcbk7iqm GET https://markdownregistry.com/api/v1/resolve?ref=striderza/opencodegamestudios/qa-plan GET https://markdownregistry.com/api/v1/blob/fea238b6e8e3bd24f90d8ccf03f08fb71c679e91f5d39a04893c059f73ab0bf8
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 striderza/opencodegamestudios
Every file in striderza/opencodegamestudios