Menu
Draft or refine the test-cases checklist for this card
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Check whether this card's code meets the acceptance criteria
Run a quick UX/UI workshop using ASCII-art sketches
Write automated tests for unticked scenarios in this card's test cases
Review code changes on this card for likely bugs, regressions, and missed edges
Cherry-pick post-merge commits onto a new follow-up branch
Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.
| name | draft-test-cases |
| description | Draft or refine the test-cases checklist for this card |
| label | Draft test cases |
| pill-order | {"specifying":9,"implementing":5} |
| jockey-hint | Surface when the card has specs but no test cases yet, or when the user wants to refresh the scenario list. Demote once a healthy test-cases file exists unless the user signals a fresh area to cover. |
| workhorse-version | 0.2.0 |
If you don't already have this card's context (title, identifier, description) — for instance when running outside Workhorse — establish it first by following .agents/docs/card-context.md.
Produce or refine the card's test-cases checklist — the concrete scenarios that verify this card is done. The file is read by both the tester running scenarios by hand and the implementing agent writing automated tests against them.
.workhorse/specs/ and any existing test cases at .workhorse/test-cases/{card-id}/.workhorse/test-cases/{card-id}/overview.md with an H1 title, an optional summary, and one or more checklist sectionsSee .workhorse/specs/test-cases/overview.md for the file's shape.