# Designing Cases

> Writes detailed test cases from a test plan, reviews quality, and publishes a test case page to Confluence. Use when a QA engineer wants to design cases, create test cases, write test cases, or expand test scenarios into detailed steps.

- Skill: `majiayu000/designing-cases` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/designing-cases`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/designing-cases/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/designing-cases

---


# designing-cases

Writes detailed test cases from a test plan, reviews quality, and publishes to Confluence.

## Progress Checklist

Copy and track your progress:

```
- [ ] Step 1: Validate prerequisites
- [ ] Step 2: Detect plan type and route
- [ ] Step 3: Write test cases per type
- [ ] Step 4: Review quality
- [ ] Validate: Scenario count + case count + quality assessment
- [ ] Step 5: Create Confluence test case pages
- [ ] Validate: Confluence URL + page count
```

## Steps

### Step 1: Validate Prerequisites

Check that `test_plan/README.md` exists and `test_plan/sections/` contains section files.

If missing: "Please run `/planning-tests` first to create the test plan."

### Step 2: Detect Plan Type and Route

Run `/tw-case-init` to read the test plan, detect the type, and route to the appropriate command:
- **Type A (Feature):** → `/tw-case-feature` — expect 20-40 cases
- **Type B (Bug Fix):** → `/tw-case-bugfix` — expect 8-15 cases
- **Type C (Enhancement):** → `/tw-case-enhance` — expect 15-25 cases

### Step 3: Write Test Cases

Execute the routed case command from Step 2. It creates `test_cases/README.md` and one `TS-XX_[Name].md` file per scenario.

Each test case needs: Objective, Preconditions, Test Steps table, Execution Type.

### Step 4: Review Quality

Run `/tw-case-review` to check all test cases for:
- Specific (not vague) actions and expected results
- Complete preconditions
- 3-10 steps per test case
- Test independence (can run standalone)

### Validate

Report:
- Total scenario count
- Total test case count
- Quality assessment: **READY FOR TESTLINK** or **NEEDS REVISION**

### Step 5: Create Confluence Pages

Run `/cf-create-page` to create test case pages in Confluence.

#### Page Naming Convention

| Source File | Page Title Format |
|-------------|-------------------|
| `README.md` | `[PROJECT_ID]: Test Cases - [Feature Name]` |
| `TS-01_*.md` | `[PROJECT_ID]: TS-01 - [Scenario Name]` |
| `TS-02_*.md` | `[PROJECT_ID]: TS-02 - [Scenario Name]` |

Create parent page first, then child pages for each TS-XX scenario.

Run `/cf-review-page` to verify formatting. Use `/cf-format-guide` for Confluence storage format reference.

**MCP tool:** `mcp-atlassian:confluence_create_page`

### Validate

Report:
- Confluence parent page URL
- Number of pages created

## Expected Input

Path to project folder containing `test_plan/README.md` and `test_plan/sections/`.

## Next Step

After designing cases, run `/syncing-testlink` to import test cases to TestLink.