to-tickets
To Tickets
Break a plan, spec, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring the tickets that block it. These are what epic-runner picks up: it works the frontier one ticket at a time, so the blocking edges you set here are the order the work actually runs in.
The tracker. Read TRACKER.md beside the repo's engineer skill — it names the tracker, gives its commands, and maps meanings to this repo's label strings. If there is none, resolve the tracker for this run from what the user gave you, the git remote, and whichever CLI is installed and authenticated; default to a directory of local markdown files when nothing resolves.
The engineer skill's directory varies by harness, so find it by glob:
ls */skills/*-engineer/TRACKER.md .*/skills/*-engineer/TRACKER.md 2>/dev/null
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.