to-ticketslisted
Install: claude install-skill praisethebit/skills
# To Tickets
## Opus guard
Do this check first, and again at the start of each turn until the skill ends. The skill ends when the tickets are published. Your system prompt names your model. If the model is not Opus and not Fable, stop. Do not do the next step. Tell the user: "This skill needs Opus or Fable. Press `s` in `/model`, pick Opus (the default) or Fable, then send your last message again."
Why: a `model:` key in a skill lasts for one turn only. Each reply of the user then goes back to the session model.
## Task
Break a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it.
## Process
### 1. Gather context
Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.
### 2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Use the `Explore` agent for the search: it runs on Haiku and returns file paths and line numbers. Read the files that the design depends on yourself. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."
### 3. Draft vertical slices
Break the work into *