Test Scenarios
phuryn/pm-skills
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Turn a requirement or user story into clear, executable test cases.
Install Test Case Writer
$ npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-case-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-case-writer .claude/skills/test-case-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-case-writer" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writer into .claude/skills/test-case-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-case-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-case-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-case-writer .agents/skills/test-case-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-case-writer" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writer into .agents/skills/test-case-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-case-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-case-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-case-writer .cursor/skills/test-case-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-case-writer" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writer into .cursor/skills/test-case-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-case-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/test-case-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-case-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-case-writer .gemini/skills/test-case-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-case-writer" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writer into .gemini/skills/test-case-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-case-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills test-case-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-case-writer .github/skills/test-case-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-case-writer" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writer into .github/skills/test-case-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-case-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-case-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-case-writer .opencode/skills/test-case-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-case-writer" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-case-writer into .opencode/skills/test-case-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-case-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-case-writer- GitHub stars
- 1.4k
- Token cost
- ~970 tokens
- SKILL.md length
- 463 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a requirement or user story into clear, executable test cases.
- Asked to write test cases
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A test suite for a feature
What it does
Test Case Writer is an agent skill from mohitagw15856/pm-claude-skills. Turn a requirement or user story into clear, executable test cases. Use when asked to write test cases, test scenarios, a test suite for a feature, or to derive tests from acceptance criteria. Produces structured test cases — preconditions, steps, test data, expected results — across happy path, edge cases, and negative cases, plus a coverage note, so a tester (or automation) can run them without guessing.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test generation and User stories. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write test cases
- A test suite for a feature
- Derive tests from acceptance criteria
Example prompts
- “/test-case-writer”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Test Case Writer loads about 970 tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 463 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 463 words, ~970 tokens.
Download SKILL.mdSave it as
.claude/skills/test-case-writer/SKILL.md (or your agent's skills folder).- name
- test-case-writer
- description
- Turn a requirement or user story into clear, executable test cases. Use when asked to write test cases, test scenarios, a test suite for a feature, or to derive tests from acceptance criteria. Produces structured test cases — preconditions, steps, test data, expected results — across happy path, edge cases, and negative cases, plus a coverage note, so a tester (or automation) can run them without guessing.
Test Case Writer Skill
Good test cases are unambiguous and complete: anyone can run them and get the same result, and together they cover the ways the feature can succeed and fail. This skill derives test cases from a requirement or user story — happy path first, then the edge and negative cases that find real bugs — each written so it's directly executable.
Working from a brief
Given a user story or a one-line feature description, write the test cases anyway — infer the acceptance criteria, boundaries, and likely failure modes, labelling assumptions. Always include edge and negative cases, not just the happy path. Never hand back questions instead of cases.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- The requirement — the feature/user story and its acceptance criteria.
- Inputs & rules — fields, valid/invalid values, limits, and business rules that define correct behaviour.
- Scope & environment — UI/API/both, platforms, and any preconditions (logged-in, data state).
- Priority — what matters most (critical paths), so cases can be ordered.
Output Format
Test Cases: [feature]
A short intro line, then cases in a table (or per-case blocks for complex flows):
| ID | Title | Type | Preconditions | Steps | Test data | Expected result | Priority |
|---|---|---|---|---|---|---|---|
| TC-01 | Valid login | Happy path | user exists | 1. … 2. … | valid creds | logged in, lands on … | High |
| TC-02 | Wrong password | Negative | user exists | … | bad password | error shown, not logged in | High |
| TC-03 | Empty fields | Negative/validation | — | … | blank | inline validation | Med |
| TC-04 | Max-length input | Edge/boundary | — | … | boundary value | accepted/handled | Med |
Cover, deliberately: happy path, boundary/edge (empty, max, min, just over/under limits), negative (invalid input, wrong state, unauthorised), and any business-rule cases.
End with a coverage note: which acceptance criteria/requirements each case maps to, and any gaps or risks to flag for review.
Show full SKILL.md (178 more words)Show less
Quality Checks
- Each case has clear preconditions, numbered steps, the test data, and a single expected result
- Steps are unambiguous — two testers would execute them identically
- Coverage includes edge/boundary and negative cases, not just the happy path
- Cases trace back to the acceptance criteria / requirement (coverage note)
- Cases are prioritised so the critical paths are obvious
- Expected results are specific and verifiable (not "works correctly")
Anti-Patterns
- Do not write only happy-path cases — the bugs live in the edges and negatives
- Do not write vague steps ("test the login") — give the exact actions and data
- Do not use unverifiable expected results ("it should work") — state the observable outcome
- Do not combine many checks into one bloated case — keep cases atomic and traceable
- Do not skip preconditions/test data — they're why a case is reproducible
Based On
Test-design practice — requirement-derived cases with boundary-value and negative testing, atomic executable steps, and traceability to acceptance criteria.
Example Trigger Phrases
- "Write test cases for this story."
- "Write test scenarios for checkout."
- "Build a test suite for this feature."
- "Derive tests from these acceptance criteria."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/test-case-writer of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Test Case Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Case Writer this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~970 | Automated safety check: Pass | MIT | |
| Test Scenariosphuryn/pm-skills | 27k | — | ~866 | Automated safety check: Pass | MIT | |
| Test Authorjpicklyk/task-orchestrator | 207 | — | ~8.2k | Automated safety check: Pass | MIT | |
| Argent QA Flowsbbplayer-app/BBPlayer | 1.2k | — | ~3.2k | Automated safety check: Pass | MIT | |
| AI Test Generationpetrkindlmann/qa-skills | 170 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Prd V07 Test Planningmattgierhart/PRD-driven-context-engineering | 180 | — | ~3.5k | Automated safety check: Notes | MIT |
Similar skills
Test Author
jpicklyk/task-orchestrator
Test authoring framework for items carrying the needs-test-author trait.
Argent QA Flows
bbplayer-app/BBPlayer
Create repeatable QA regression E2E tests as Argent flows from test cases, tickets, or acceptance criteria.
AI Test Generation
petrkindlmann/qa-skills
Use AI to write NEW test code from specs, PRDs, user stories, code diffs, bug reports, or OpenAPI specs.
Prd V07 Test Planning
mattgierhart/PRD-driven-context-engineering
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution.
Test Case Management
petrkindlmann/qa-skills
Author and maintain MANUAL and hybrid test cases and suites in TestRail, Xray (Jira), Zephyr Scale, and Qase.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Test Case Writer
What does Test Case Writer do?
Turn a requirement or user story into clear, executable test cases. Test Case Writer is an agent skill from mohitagw15856/pm-claude-skills. Turn a requirement or user story into clear, executable test cases.
When should I use Test Case Writer?
Test Case Writer fits situations like: asked to write test cases; A test suite for a feature; derive tests from acceptance criteria.
How do I install Test Case Writer in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a claude-code`. Or copy the skill folder (skills/test-case-writer in mohitagw15856/pm-claude-skills) into .claude/skills/test-case-writer in your project. Claude Code loads it when a task matches its description.
How do I install Test Case Writer in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a codex`. Or copy the skill folder (skills/test-case-writer in mohitagw15856/pm-claude-skills) into .agents/skills/test-case-writer in your project. Codex loads it when a task matches its description.
Can I use Test Case Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-case-writer, .gemini/skills/test-case-writer, .github/skills/test-case-writer and .opencode/skills/test-case-writer in your project.
What does Test Case Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Case Writer is instructions for the agent only.
Does Test Case Writer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Test Case Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Case Writer use?
Test Case Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Case Writer use?
About 970 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Case Writer?
Skills that share tags, products or a category with Test Case Writer: Test Scenarios (phuryn/pm-skills, 27k stars), Test Author (jpicklyk/task-orchestrator, 207 stars), Argent QA Flows (bbplayer-app/BBPlayer, 1.2k stars) and AI Test Generation (petrkindlmann/qa-skills, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Case Writer?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.