# create-test-cases

create-test-cases drafts browser-focused manual test cases in Markdown for a project feature or area. Use it to prepare cases for /qa:manual-test-run.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 406 repo stars
- Author: syahiidkamil
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/syahiidkamil/Software-Engineer-AI-Agent-Atlas/tree/HEAD/.claude/commands/qa/create-test-cases.md
- Updated: 2026-11-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/create-test-cases

## What it does

The command examines the selected feature and relevant project material, then writes files under `docs/living-test-cases/{feature-slug}/`. The folder contains a `README.md` index and separate `TC-{NNN}.md` files with a test type, priority, prerequisites, actions, and observable expected results.

Cases can cover core flows, error handling, and unusual states. Each action should be clear enough to perform without guessing, and each result should be visible in the browser. The output is Markdown, not test-framework code. If you omit the feature or area, the command asks what to cover; an outcome the browser cannot show may be marked UNSURE by the runner.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/create-test-cases.md` — Call it with /create-test-cases. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/create-test-cases.md` — Call it with /prompts:create-test-cases. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/create-test-cases.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/create-test-cases.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/syahiidkamil/Software-Engineer-AI-Agent-Atlas/tree/HEAD/.claude/commands/qa/create-test-cases.md

## When to use it
- document manual checks for a feature
- turn a user flow into explicit test steps
- record visible expected outcomes in Markdown
- cover invalid input and unusual states

## Example prompts
- Write manual test cases for the checkout flow.
- Create browser checks for the profile page.
- Draft cases for data import, including invalid input.

## Similar
- [test-cases](https://affpapa.org/en/nevibecode/skills/test-cases.md) — skill · 1300 installs
- [test-plan](https://affpapa.org/en/nevibecode/rules/test-plan.md) — rule · ★ 267 repo stars
- [breakdown-test](https://affpapa.org/en/nevibecode/skills/breakdown-test.md) — skill · 9264 installs
- [om-prepare-test-env](https://affpapa.org/en/nevibecode/skills/om-prepare-test-env.md) — skill · 3900 installs
- [test-reliability](https://affpapa.org/en/nevibecode/skills/test-reliability.md) — skill · 1500 installs
- [sap-sac-test-automation](https://affpapa.org/en/nevibecode/skills/sap-sac-test-automation.md) — skill · 695 installs

From the same set: [syahiidkamil/software-engineer-ai-agent-atlas](https://affpapa.org/en/nevibecode/by/syahiidkamil/software-engineer-ai-agent-atlas.md) — 26 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
