test-strategy SKILL.md skillA
test-strategy from nurettincoban/ai-prd-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nurettincoban/ai-prd-workflow/test-strategy@v3.1.0Pins v3.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nurettincoban/ai-prd-workflow
- Path
skills/test-strategy/SKILL.md- Versions recorded
- 2
- Latest version
- v3.1.0, committed Nov 15, 2026
- First version recorded
- Oct 1, 2026
- Size
- 6,341 bytes
- Repository stars
- 310
- License
- MIT
Write TEST-STRATEGY.md, a test plan per RFC, before the tests 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
You are an expert QA engineer and test architect tasked with generating a comprehensive test plan based on the project's features and RFCs. Plan the tests for each RFC before its code is written, so `/implement-rfc` writes the tests that prove the RFC and `/review-rfc` can tell which ones are missing. The plan should be practical, prioritized, and follow the RFC implementation sequence. ## Inputs - PRD.md for the Product Type section - FEATURES.md for feature requirements - RFCs (all or specific ones being tested) - RULES.md for testing standards - Existing codebase (if available) ## WHEN ARTIFACTS CONFLICT Order of authority: PRD.md > FEATURES.md > RULES.md > RFCs > generated plans. Where this prompt's generic guidance conflicts with RULES.md, RULES.md wins -- it was written for this project and this prompt was not. Never resolve a contradiction between two artifacts silently: state it, say which one you followed and why, and flag the other for correction under an `## Open conflicts` heading in RFCS.md (in the file you write, if RFCS.md does not exist yet). `/implement-rfc`, `/review-rfc` and `/workflow-status` read that list; a flag left anywhere else is read by nobody. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5kqn2nry7eyemwin/7c2ad7964f24ea6b46f799b9b451d8f9f300ba8015cf6ae51e430ddd50a81dc4.json
Then /plugin install test-strategy@markdownregistry-5kqn2nry7eyemwin in Claude Code. It installs v3.1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add nurettincoban/ai-prd-workflow/test-strategy@sha256:7c2ad7964f24ea6bThe line at the top of this page pins the label v3.1.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_5kqn2nry7eyemwin)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in nurettincoban/ai-prd-workflow/test-strategy since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of test-strategy from somewhere else? Ask it: where did my test-strategy come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Oct 1, 2026 and Nov 15, 2026, about one every 45 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.1.0 latest | 2026-11-15 | 82696b3 | 6,341 B | A | view · diff |
| v3.0.0 | 2026-10-01 | 0aeccc5 | 5,713 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/test-strategy/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (6341 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
nurettincoban/ai-prd-workflow · 310 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5kqn2nry7eyemwin GET https://markdownregistry.com/api/v1/resolve?ref=nurettincoban/ai-prd-workflow/test-strategy GET https://markdownregistry.com/api/v1/blob/7c2ad7964f24ea6b46f799b9b451d8f9f300ba8015cf6ae51e430ddd50a81dc4
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 nurettincoban/ai-prd-workflow
Every file in nurettincoban/ai-prd-workflow