To Tickets

Break a plan, specification, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it.

The issue tracker, ticket-writing convention, and triage role vocabulary should have been provided to you. If not, ask the user whether to run /setup-ai-workspace now; if they decline, stop and tell them this skill needs it before continuing.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a specification path, an issue number or URL) as an argument, fetch it and read its full body and comments.

Read the "Ticket writing convention" section of documentation/agents/issue-tracker.md. It names either the built-in templates below or an optional project convention such as an issue-template document or a ticket-writing skill. If the configured convention points to another source, read that source before drafting.

Confirm the convention with the user before applying it. Present the configured convention as the recommendation and the built-in to-tickets format as the fallback. A named skill supplies ticket structure and quality rules only; this skill still owns decomposition, blocking edges, approval of the breakdown, and the save-versus-publish boundary. If the tracker configuration predates this setting, ask which convention to use for this run, then continue without requiring the user to re-run setup.

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.