to-tickets

Topics in the source

• To Tickets
• Process
• 1. Gather context
• 2. Explore the codebase (optional)
• 3. Draft vertical slices
• 4. Quiz the user
• 5. Publish the tickets to the configured tracker
• :

Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it. The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills. 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. 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." Break the work into tracer bullet tickets. Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer A completed slice is demoable or verifiable on its own Each slice is sized to fit in a single fresh context window Any prefactoring should be done first Give each ticket its blocking edges: the other ticke

This is an excerpt. Refer to the complete source and its current requirements.