Retest Bug (discovery stub)

Thin entry for agent skill discovery. Full procedure: WORKFLOW.md.

When invoked:

1. Announce once: Using **retest-bug-workflow** to retest the bug fix.
2. Settle and strategize first — before any tool call, follow settle-and-strategize.md: invoke engineering:testing-strategy to plan the retest approach, no guessing an expected/spec, no blind retry loops.
3. Design (Figma) comparison is mandatory on every UI retest — figma-design-comparison.md. A screen with no design reference is reported back to the person or channel that assigned the retest and its visual points stay BLOCKED; never assume a label, order, or layout.
4. Retest deeply — customer-escape-prevention.md: cover the whole surface the fix touched, measure overflow/overlap at every in-scope width, evidence on passed rows too, and never PASSED over a "cannot verify" actual result.
5. Read and follow WORKFLOW.md end-to-end — every step, gate, and reference.

Claude Code shortcut: /retest-bug → commands/retest-bug.md.

Refusal-first (precondition gate)

All preconditions and refusal rules are in WORKFLOW.md. MUST NOT start without a Jira issue key/URL — a Bug, or a Task / Story whose fix is being re-verified — and reachable environment config.

QA closing (mandatory before "done")

All close-out gates are in WORKFLOW.md and verify-closing-checklist.md (Retest section). MUST NOT claim PASSED/FAILED without evidence in the comment, and MUST NOT post a retest comment — bug or task — without its case list (Test cases run table: Case · Title · Covers · Role · Status — the design reference goes on the header's Design ref: line, never as a per-row column).