dispatch-ticketlisted
Install: claude install-skill thientranhung/astragentic
# Dispatch a ticket — shared protocol
Role contract: `.agents/roles/builder.md`. Runtime, model and effort per role:
`.agents/orchestrator.md`, read at session start; an edit takes effect at the next dispatch.
Every role runs on Claude Code. **The launcher, the mod and pre-dispatch verification live in
`dispatch-ticket-claude`**; read both skills.
## The sequence
1. **Preflight, first dispatch of the session** — watchdog running (`WATCHING.md` § watchdog),
payload committed (below).
2. **Resolve the row** — runtime, model, effort from `orchestrator.md`; collect the write-set.
3. **Claim, then create branch and worktree** — the claim protocol is `thomas.md`'s.
4. **Resolve the workspace**, create the tab and pane, pass the cwd gate.
5. **Print the resolved dispatch**, launch (`dispatch-ticket-claude`), read the record back.
6. **Submit the brief** — first line is the phase's plugin-qualified slash command.
7. **Branch on the pane's turn end** — `TURN-END` for a mod pane, the watcher's exit for a gate or junior pane.
8. **Verify by artifact**, then cleanup — [`CLEANUP.md`](CLEANUP.md).
## The binding identity
```text
ticket → assignee (the claim) → pane → worktree → branch → PR
```
Each link is one-to-one. Parallel tickets get their own pane, session, worktree and branch;
sequential tickets may reuse a workspace but take fresh tabs. The claim precedes the worktree
(`thomas.md` § claim protocol); the sole-writer rule is the Builder's (`builder.md`).
## Inputs and resol