to-tickets
To Tickets
Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it.
This repo tracks work in GitHub Issues. Use the gh CLI, which infers the repository from the clone.
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. Before exploring, read GLOSSARY.md at the repo root (or GLOSSARY-MAP.md and the per-context glossaries it points at) and the ADRs under docs/adr/ or src/*/docs/adr/ that touch the area. If they don't exist, proceed silently and don't create them. Ticket titles and descriptions should use the project's domain glossary vocabulary, and surface any ADR conflict rather than silently overriding it.
Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."