codegenlisted
Install: claude install-skill sjzavala/claude-qa-tms
# Generate a traceable Playwright spec
Input: **$ARGUMENTS** — one or more case IDs in `<PROJECT>-<n>` form, exactly as Qase displays them (e.g. `ACME-42`). If empty, ask which case(s), or use the ones just verified in this conversation.
## Step 1 — Resolve each ID, then fetch the case
Split each argument on the **last** hyphen: left side is the project `code`, right side is the numeric `id`. So `ACME-42` → `{code: "ACME", id: 42}`.
`qase_get` with `{entity: "case", code: "<PROJECT>", id: <n>}` per ID — `id` as a number, never the combined string. Take the code from the argument itself; the examples here are illustrative only. You need: title, suite, priority, preconditions, and each step's action + expected result. Fall back to `test-cases/` locally if Qase is unavailable.
Keep **both** forms — the spec needs each in a different place (see `references/spec-template.md`):
| Where | Form | Shape (for `ACME-42`) |
|---|---|---|
| `@qase-id` JSDoc line | display | `ACME-42` |
| Playwright `tag` | display, prefixed | `@qase:ACME-42` |
| `@qase-url` | split | `https://app.qase.io/case/ACME/42` |
| `qase.id()`, if the reporter is already a dep | numeric | `qase.id(42)` |
A spec generated from only the numeric id loses its trace back to the case.
Tool names and params: `references/qase-tools.md` — the published Qase README is wrong about several of them.
If a case reads vaguely and you find yourself guessing at selectors, the case is the problem, not the spec. `references/c