test-plan
Skill0 starsChanged 17 days agoMITView on GitHub
Create a full test plan or test strategy document for a feature, release, or project. Use when the user asks for a test plan, test strategy, or QA planning for a release.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- huntie/skillstheir own version, first seen Nov 1, 2026
- TzolkinB/skillstheir own version, first seen Oct 22, 2026
- DoKu67/claude-code-skilstheir own version, first seen Oct 16, 2026
- AviadP/aviad-dev-toolkittheir own version, first seen Oct 15, 2026
- vhmarquez/argotheir own version, first seen Oct 15, 2026
- XGENT-ai/skillstheir own version, first seen Oct 13, 2026
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- liferay/liferay-portal★ 2.3ksame name
- stackrox/stackrox★ 1.3ksame name
- MillenniumDawn/Millennium-Dawn★ 161same name
- mbwsims/claude-universe★ 71same name
- Codagent-AI/agent-skills★ 31same name
- katalon-labs/true-skills★ 10same name
- yasunori0418/skills★ 9same name
- xmh-test/test-agent-skills★ 5same name
- DoKu67/claude-code-skils★ 4same name
- SUDARSHANCHAUDHARI/QACraft★ 2same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-testSkill
- automateSkill
- bug-reportSkill
- exploratorySkill
- mobile-testSkill
- test-casesSkill
- test-dataSkill
- test-reportSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a practical test plan document.
- Very specific: line 12
Write the plan as a markdown file in the project (e.g.
- Very specific: line 23
Keep it lean — a plan people will actually read (1-2 pages), not a 20-page template.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Plan Builder
Create a practical test plan document. Ask the user first (briefly, max 3 questions) about: what is being tested, the deadline/timeline, and the team size — unless they already said.
Document structure
Write the plan as a markdown file in the project (e.g. test-plans/<feature>-test-plan.md) with these sections:
- Overview — what is being tested, in 2-3 sentences
- Scope — In scope / Out of scope (explicit lists)
- Test Approach — which test types apply: functional, regression, API, UI, cross-browser/device, performance, security, accessibility. For each, say why it applies or is skipped.
- Entry / Exit Criteria — when testing starts, when it's done (e.g. "all P1/P2 defects fixed, 95% test cases executed")
- Test Environment & Data — environments, accounts, test data needs
- Risks & Mitigations — realistic risks (tight timeline, unstable environment, missing requirements)
- Schedule & Estimates — rough phases with effort
- Deliverables — test cases, defect reports, summary report
Keep it lean — a plan people will actually read (1-2 pages), not a 20-page template. Mark anything you assumed with (assumption) so the tester can confirm with the team.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

