To Tickets

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

Output destination

Settle this before drafting, so you know what shape the blocking edges take. Tickets always get written somewhere; the only question is where.

First, ask whether to publish

Ask first — never assume, and never publish to a tracker the user hasn't agreed to:

Do you want these tickets published to an issue tracker, or written as local markdown files in your OS temp directory?

If they want them published, find the tracker

Look in the agent instructions you were given — AGENTS.md, CLAUDE.md, or whichever instruction files this project uses — plus any tracker configuration they point to, for a named tracker. It counts as available only if you can both name it (GitHub, Linear, Jira, …) and reach it with the tools you have.