Ticket
The delivery loop, as one skill. The human names the action:
/ticket load <ticket>
/ticket start
/ticket review
/ticket complete
Process
- Take the action from the invocation.
If none was given, list the four actions below and stop.
If it is not one of the four, say so, list them, and stop.
- Read only
skills/ticket/actions/<action>.md and follow it exactly.
Actions
load — prepare one ticket for execution. Resolves the ticket store, reads
the ticket and its parent Feature spec, verifies every blocker, loads the
minimum context the ticket names, and writes the session's workspace state.start — implement the loaded ticket, restating the pre-implementation
summary before editing anything.review — verify implemented work against the ticket and its parent Feature,
and report findings. It changes no implementation and accepts nothing.complete — complete work the human has accepted, through the project's
delivery workflow and its durable records, then name the tickets that are now
ready.
Lifecycle
A ticket's status holds the durable lifecycle state named in
context/ai-interaction.md. It lives in the ticket store — see
skills/ticket/store.md, which is where the store and ticket identity are
defined:
Proposed → Ready → In Progress → Complete
Cancelled and Superseded are terminal alternatives.
load writes Proposed → Ready.start writes Ready → In Progress.complete writes Complete.review writes no status. Review is workflow activity, not lifecycle state.
The parent Feature's status is derived from its tickets, never maintained by
hand. start and complete are the only actions that write it, and each writes
it only as a consequence of the ticket transition it just made.
context/current-ticket.md is transient workspace state and records no status.
Rules
- Run the one action the human named. Do not continue into the next one.
- Read only that action's file. The other three are not context for this work.
- One ticket at a time. A session that finishes a ticket stops there.
- Human authority is unchanged: approval, acceptance, merge, and release are
the human's, whichever action is running.
1---2name: ticket3description: Run one action of the ticket delivery loop — load, start, review, or complete.4---56# Ticket78The delivery loop, as one skill. The human names the action:910`/ticket load <ticket>`11`/ticket start`12`/ticket review`13`/ticket complete`1415## Process16171. Take the action from the invocation.18 If none was given, list the four actions below and stop.19 If it is not one of the four, say so, list them, and stop.202. Read only `skills/ticket/actions/<action>.md` and follow it exactly.2122## Actions2324- `load` — prepare one ticket for execution. Resolves the ticket store, reads25 the ticket and its parent Feature spec, verifies every blocker, loads the26 minimum context the ticket names, and writes the session's workspace state.27- `start` — implement the loaded ticket, restating the pre-implementation28 summary before editing anything.29- `review` — verify implemented work against the ticket and its parent Feature,30 and report findings. It changes no implementation and accepts nothing.31- `complete` — complete work the human has accepted, through the project's32 delivery workflow and its durable records, then name the tickets that are now33 ready.3435## Lifecycle3637A ticket's status holds the durable lifecycle state named in38`context/ai-interaction.md`. It lives in the ticket store — see39`skills/ticket/store.md`, which is where the store and ticket identity are40defined:4142`Proposed` → `Ready` → `In Progress` → `Complete`4344`Cancelled` and `Superseded` are terminal alternatives.4546- `load` writes `Proposed` → `Ready`.47- `start` writes `Ready` → `In Progress`.48- `complete` writes `Complete`.49- `review` writes no status. Review is workflow activity, not lifecycle state.5051The parent Feature's status is derived from its tickets, never maintained by52hand. `start` and `complete` are the only actions that write it, and each writes53it only as a consequence of the ticket transition it just made.5455`context/current-ticket.md` is transient workspace state and records no status.5657## Rules5859- Run the one action the human named. Do not continue into the next one.60- Read only that action's file. The other three are not context for this work.61- One ticket at a time. A session that finishes a ticket stops there.62- Human authority is unchanged: approval, acceptance, merge, and release are63 the human's, whichever action is running.
rikilamadrid