testcase-artisanlisted
Install: claude install-skill zhuhrymhd/quality-atelier
# Testcase Artisan
Turns project documentation into structured, maintainable test case specifications.
Read this whole file before doing anything - the steps below depend on each other.
## Boundary
This skill produces one thing: markdown files describing what should be tested and
why, under `docs/test-cases/`. It never writes XCTest/XCUITest/Jest/etc. code, and it
never runs a build or a simulator. If the user asks to actually implement or run
tests, that's testrun-forgemaster's job.
The `Level test` field this skill writes on each test case is the reference that
downstream skills follow. testrun-forgemaster implements each test case at the level
written here; if it thinks another level fits better, it only records that as a
suggestion in its report and never changes these files. So classify `Level test`
carefully using the rule in `references/field-format.md` - it is not a loose hint.
## Step 1: Figure out the mode
There is no special phrasing for "generate" vs "update" vs "audit" - infer the mode
from what's on disk and what the user asked for:
- User named a specific feature (or one is obvious from context) → **scoped mode**.
Check whether `docs/test-cases/<feature>.md` already exists.
- Doesn't exist → **generate**: build the file from scratch (Step 4 onward).
- Exists → **update**: read it first, then reconcile against current docs (Step 5).
- User asked something like "what's missing", "audit coverage", or gave no specific
feature at all → **gap-audit mod