test-case-writer
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.
npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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, t
- Working from a brief
- Required Inputs
- Output Format
- Test Cases: [feature]
- Quality Checks
- Anti-Patterns
- Based On
What does the test-case-writer skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill test-case-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.