test-plan-writer SKILL.md skillA
test-plan-writer from wst2002/claude-code-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wst2002/claude-code-skills/test-plan-writer@git:20261016.55bd98aPins git:20261016.55bd98a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wst2002/claude-code-skills
- Path
skills/test-plan-writer/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261016.55bd98a, committed Oct 16, 2026
- First version recorded
- Oct 16, 2026
- Size
- 2,737 bytes
- Repository stars
- 3
- License
- MIT
Use when writing a test plan or test strategy for a release, feature, sprint or project, defining QA scope, risks, test types, environments, entry and exit criteria, or estimating testing effort.
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 Plan Writer ## Overview A test plan decides where testing effort goes and when the product is good enough to ship. Drive it by risk: test hardest what would hurt users or the business most if it broke. ## Method 1. **Understand the release:** features and changes (PRD, tickets, changelog, diff), affected areas, integrations, deadlines, team size. 2. **Assess risk** for each area: impact if it breaks × likelihood (new code, complex logic, past bugs, many integrations). Rank areas high, medium, low. 3. **Choose test types per area** based on risk: functional, regression, integration, API, end-to-end, performance, security, accessibility, compatibility, exploratory. 4. **Define environments and data:** where tests run, browsers and devices, test accounts, data setup and reset. 5. **Set entry and exit criteria** that can be checked objectively. 6. **Estimate and schedule** effort per area; note what is automated vs manual. 7. **Write** using the format below; keep it to what the team will actually use. ## Format ``` # Test Plan — <release / feature> 1. Scope In scope: <features, platforms> Out of scope: <and why> 2. Risk assessment …
Read the whole file at its exact version.
How to install
mdr add wst2002/claude-code-skills/test-plan-writer@sha256:2097e996783fec98The line at the top of this page pins the label git:20261016.55bd98a, 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_cc63hh7px5b2zckp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 16, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.55bd98a latest | 2026-10-16 | 55bd98a | 2,737 B | A | view · diff |
| git:20261016.de13fc3 | 2026-10-16 | de13fc3 | 2,535 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 (2737 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
wst2002/claude-code-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cc63hh7px5b2zckp GET https://markdownregistry.com/api/v1/resolve?ref=wst2002/claude-code-skills/test-plan-writer GET https://markdownregistry.com/api/v1/blob/2097e996783fec98de1fb3f701cdb5f94eb545d816388a41cc2ca3f5a66ba795
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.