To Tickets

Break a plan, spec, or conversation into small, focused tickets, each covering one concrete task with minimal context and 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 /ai-setup-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.