To Tickets

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

Interaction Method

Use the platform's blocking question tool for quiz and confirmation steps: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini/Pi/Cursor. Fall back to numbered options in chat only when no blocking tool exists or the call errors. Ask one question at a time.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a spec issue, a plan comment, 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."