test-plan-writer
Skill1 starsChanged 21 days agoNo licenceView on GitHub
Write a test plan for a ticket, feature, or change as an end-to-end user journey rather than a checklist of acceptance criteria. Walks the workflow the way a real user would, confirms existing business logic still holds, and puts the effort on the edge cases that survive normal testing — records created before the change, the thing that got removed, missing optional data, stale state after a switch. Generates the questions to ask engineering about which fields and collections a change touches instead of guessing at them. Use when asked to write or review a test plan, a QA plan, UAT steps, a validation plan, or test cases for a ticket; when asked how to test a feature or what could break; or when a test plan reads like restated acceptance criteria and needs rewriting as a journey.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- WST2002/claude-code-skillstheir own version, first seen Oct 17, 2026
- 45ck/documentation-evidence-skillstheir own version, first seen Mar 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- WST2002/claude-code-skills★ 4same name
- 45ck/documentation-evidence-skills★ 2same name
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 repository30 other files it gives its agents.
- artifact-documentorSkill
- cohere-bug-triageSkill
- cohere-config-doc-writerSkill
- cohere-initiative-doc-writerSkill
- cohere-pcr-writerSkill
- cohere-rca-investigatorSkill
- communication-skill-typesSkill
- councilSkill
- crisp-test-plan-writerSkill
- dev-signoff-writerSkill
- eod-context-updaterSkill
- eod-updaterSkill
- framework-writerSkill
- grill-meSkill
- grooming-notes-updaterSkill
- jira-ticket-writerSkill
- marketing-psychologySkill
- market-researchSkill
- meet-a-userSkill
- mom-trackerSkill
- mom-writerSkill
- po-review-helperSkill
- product-roadmap-scopingSkill
- ram-writing-styleSkill
- release-notes-writerSkill
- slack-mcp-troubleshooterSkill
- slack-question-writerSkill
- speed-reading-skillSkill
- the-humanizerSkill
- write-a-skillSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 18 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.