Individual skill
test-case-designer
Converts requirements into structured manual and automated test cases with clear steps and expected results. Use when you need a test plan/test case document, not code-level unit tests.
skills/testing/test-case-designer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 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)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,325 bytesSKILL.mdcore · 2,624 bytesexamples/example.mddoc · 2,328 bytes
Read excerpt
## Purpose
Convert a set of requirements (functional spec, user story, acceptance criteria) into structured test cases — the kind used for manual QA or as a blueprint for automated test scripts — each with clear preconditions, steps, and expected results.
## When to Use
- Requirements exist (or were just extracted, e.g. via [Requirements Extractor](../../reasoning/requirements-extractor/)) and need a test plan before or during implementation.
- QA needs a structured document to execute manually.
- Preparing acceptance criteria for a feature sign-off.
Differs from [Test Generator](../test-generator/): this produces human-readable test *cases* (steps + expected results, framework-agnostic), not executable code.
## What to Analyze / Do