← ClaudeAtlas

ticketlisted

Drive one tracked ticket from arrival to resolution through four verbs: triage, start, revise, finalize. Use when the user says triage/start/revise/finalize with a ticket id, asks to turn a ticket into a locked brief, to execute a work order, to action a review round on a ticket's pull request, or to close out a merged ticket. Literal triage, start, or revise invocation requests the work order or task prompt plus only needed repository code and documentation for every mandatory worker dispatch, including nested review and nested Orchestrate work: to OpenAI's Codex model service for a Codex UI parent, or OpenAI's Codex model service or Anthropic's Claude model service for a Claude Code parent. Credentials, secrets, patient data, `.env`, and real database contents are excluded. Automatic activation outside an invoked parent workflow asks once before dispatch; finalize grants no worker-egress consent.
ConnorGriffin/skills · ★ 20 · AI & Automation · score 66
Install: claude install-skill ConnorGriffin/skills
# Ticket One ticket, one verb at a time. Each verb is a full procedure in `verbs/<verb>.md`; read that file before doing anything else, then follow it. This page holds only what every verb shares. ## Invocation `/ticket <verb> <ticket-id>`, where verb is `triage`, `start`, `revise`, or `finalize`. No verb or no ticket id: ask for it, one line. Unknown verb: list the four. Literal user invocation of `/ticket triage`, `/ticket start`, or `/ticket revise` requests the bounded transfer needed for every mandatory worker dispatch the selected workflow routes, including nested review and nested Orchestrate work. The payload is the work order or task prompt plus only the repository code and documentation needed for that delegated task. For a Codex UI parent, the destination is an isolated worker on OpenAI's Codex model service. For a Claude Code parent, existing routing selects an isolated worker on OpenAI's Codex model service or Anthropic's Claude model service. Credentials, secrets, patient data, `.env`, and real database contents are excluded. Automatic activation outside an invoked parent workflow does not acquire this consent. Before the first external dispatch it asks once, naming the same payload, applicable destination or destination matrix, and exclusions; a denial stops the workflow. `/ticket finalize` grants no worker-egress consent because it routes no model dispatch. ## The pipeline * `triage` reads the ticket and the repo, interviews the user through `/scope`