dispatch-qa-walklisted
Install: claude install-skill thientranhung/astragentic
# Dispatch QA: walk, probe or verify
Role contract: `.agents/roles/qa.md`. The gate worktree, the pane, the brief's common fields and
the collection checks are in `dispatch-ticket/GATE.md` and are **not restated here**. That file is
their one home. This skill owns what a QA run needs and the other gates do not.
## When it fires: count, do not judge
**Before a PR, a merge or a release**, on anything with a user-visible surface or a public
endpoint. Whether a change touched a surface is a judgement about your own workload, and a gate
that fires on a judgement starves. Measured three times on three designs: a browser walker that
shipped across releases and never ran once, and nine fold rounds in half a day with one merge in
which QA was never dispatched at all.
So carry a counter. **More than 10 merges touching a user-visible surface or a public endpoint
since the last run is a STOP.** Dispatch QA, or write down why not. "None touched a surface" is a
valid answer. Not having counted is not.
A project with no user-visible surface, no public endpoint and no job or pipeline anyone
depends on skips, and says so. A jobs-only product is not that project: it gets `verify`.
## Pick the mode from the ticket's surface
One plan, three modes. Read the surface from the plan, not from the diff's file names.
| The ticket changes | Mode | QA does |
|---|---|---|
| screens, journeys, links | walk | uses the UI as the user: journeys, numbers across screens, deeplinks, end-of-journey links