Phase 06 · Test Design

The Test Skill reads scenario diagrams and writes structured test cases — unit tests and integration tests — before a single line of business code is written. This is test-first at the design level, not just the code level.

What it produces

logos/resources/test/ containing Markdown test case documents:

UT-S01.md   — unit test cases for scenario S01
IT-S01.md   — integration test cases for scenario S01

Each test case has a unique ID (e.g., UT-S01-01) that persists through the entire Spec Chain — from design to code to verification.

Test case format

## UT-S01-01 — Register with valid email and password

**Type**: Unit
**Scenario**: S01 step 2
**Input**: `{ email: "user@example.com", password: "Secure1!" }`
**Expected**: Returns `{ user_id: string, token: string }`, status 201
**Edge cases**: Duplicate email → 409 Conflict

Why before code?

Writing test cases from scenarios forces you to identify gaps in the design — missing edge cases, ambiguous acceptance criteria, undefined error states — while they're still cheap to fix.

When you reach Phase 07 (Code Generation), the AI receives both the spec and the test cases. It knows exactly what "correct" means.

Next step

→ Phase 07 · Code Generation