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. If the spec contains Gherkin scenarios (from /mattpocock:bdd), each ticket should map to one or more scenarios; the scenarios are the authoritative acceptance criteria.
The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /mattpocock:setup-matt-pocock-skills.
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. 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."