to-tickets

name	to-tickets
description	Break a plan, spec, or the current conversation into a set of tracer-bullet todos, each declaring its blocking edges — create-then-wire so every blocker id is real.
disable-model-invocation	true

To Tickets

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

The tracker backend and vocabulary are defined in ../todo-tracker.md (the todo-tracker skill). Read it before publishing — it defines the todo tool mapping, status vocabulary, tag names, Blocked by: body convention, and the frontier algorithm.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a spec path, a todo id) as an argument, fetch it and read its full body.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Todo 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."

3. Draft vertical slices

Break the work into tracer bullet tickets.

• Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer
• A completed slice is demoable or verifiable on its own
• Each slice is sized to fit in a single fresh context window
• Any prefactoring should be done first

Give each ticket its blocking edges — the other tickets that must complete before it can start. A ticket with no blockers can start immediately.

Wide refactors are the exception to vertical slicing. A wide refactor is one mechanical change — rename a column, retype a shared symbol — whose blast radius fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as expand–contract. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.

4. Quiz the user

Present the proposed breakdown as a numbered list. For each ticket, show:

• Title: short descriptive name
• Blocked by: which other tickets (if any) must complete first
• What it delivers: the end-to-end behaviour this ticket makes work

Ask the user:

• Does the granularity feel right? (too coarse / too fine)
• Are the blocking edges correct — does each ticket only depend on tickets that genuinely gate it?
• Should any tickets be merged or split further?

Iterate until the user approves the breakdown.

5. Publish todos via create-then-wire

Publish the approved tickets as todos using a two-pass approach:

Pass 1 — create all todos (no blockers yet):

Create each todo in dependency order (blockers first) with status: "ready-for-agent" and tag enhancement. Leave the body blocker-free for now; you need real ids first.

todo({
  action: "create",
  title: "<ticket title>",
  status: "ready-for-agent",
  tags: ["enhancement"],
  body: "## What to build\n\n<end-to-end behaviour from the user's perspective>\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2"
})
// → returns { id: "TODO-xxxxxxxx", ... }

Record every returned TODO-xxxx id against its title.

Pass 2 — wire blockers:

For each todo that has blockers, update its body to prepend a Blocked by: line using the real ids collected in pass 1:

todo({
  action: "update",
  id: "TODO-yyyyyyyy",
  body: "Blocked by: TODO-xxxxxxxx\n\n## What to build\n\n...\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2"
})

A todo with no blockers gets no Blocked by: line — it is on the frontier immediately.

Do NOT close or modify any parent issue or spec todo.

In either form, avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Work the frontier one ticket at a time with /implement, clearing context between tickets.