Individual skill

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.

plugins/pm-qa/skills/test-case-writer/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top