review-ticket

# Review ticket A pre-pickup triage glance: read a ticket — or a set of tickets forming one feature — usually before anyone has started it, and decide whether it can be picked up or something must be clarified first. The output briefs the developer on the feature and lists the questions worth asking whoever owns the requirements. ## Input - **Local ticket document(s)**: a single `.TICKET.md`, several, a ticket-set directory, or a `.TICKET.md` whose `## Ticket set` section lists siblings. - **One or more ticket URLs or bare ids/keys**: delegate — even for a single one — to a subagent that invokes [fetch-ticket](../fetch-ticket/SKILL.md), so the tickets land on disk without the fetch bloating this session's context, then review the local files. If the input is ambiguous or unrecognized, ask rather than guess. **Set mode** applies to multiple tickets, a set directory, or a `.TICKET.md` listing a `## Ticket set`. For a lone member file whose intended scope isn't obvious from the request, ask whether to review the whole set or just that ticket. ## Read the materials Read the input ticket file(s), **visually inspecting the downloaded images and design frames** — they are part of the spec and often where the gaps hide. **Widen only on demand.** When the input already tells the feature clearly — the journey, the why, what each ticket delivers — review it as-is: reading beyond the input is never a required step. Settle a specific doubt as cheaply as possible, and only to...