ticket-states
Installation
SKILL.md
Ticket states
A ticket's state says who acts next. The tracker owns lifecycle: claims, blocking edges, deferral, and closing. These states record only what the tracker can't: whether a ticket is designed, approved, or waiting on a human.
States
| State | Meaning | Set by | Cleared by |
|---|---|---|---|
| (none) | Untriaged: nobody has looked at it | whoever triages it | |
needs-design |
Real work; design is the next step | whoever triages it; /build-ticket stopping for redesign |
/to-tickets |
ready-for-agent |
Designed and approved by a human; an agent may pick it up | /to-tickets; a human answering |
/build-ticket |
needs-human |
An agent needs a decision or an answer; a comment on the ticket says what | /build-ticket stopping on a question, or on a failed verification it can't fix |
whoever answers it |
needs-review |
Built with evidence, still claimed, not yet landed | /build-ticket hand-off |
closing the ticket |