Skip to content
Get packs

To Tickets

Splits a plan or conversation into dependency-linked tickets and publishes them to a tracker or local files.

Source Download skill
Repository
mattpocock/skills
Stars
309,658
Licence
MIT
Files
2 files

What it does

When installed, the agent turns a plan, spec, or current conversation into a set of small, end-to-end work tickets, each listing which other tickets must finish before it can start. It proposes the breakdown, asks you to approve or adjust it, and then writes the tickets either as one markdown file per ticket in a local folder or as real issues on your configured tracker such as GitHub or Linear. It can also handle large mechanical refactors by sequencing them into expand, migrate and contract steps.

Great for

  • Engineering leads who want a feature split into agent-ready tasks with clear dependency order
  • Developers using Matt Pocock's skills setup who already have an issue tracker or a local .scratch workflow configured
  • Teams planning multi-step refactors that touch many call sites

Skip it if

  • Solo non-technical users with no issue tracker or planning workflow, since the output assumes a tracker or repo setup (the skill depends on a prior setup step)
  • Cases where you want the agent to act without review: the skill requires you to approve the breakdown, and publishing creates real issues that others may see
  • Projects without a configured tracker: the skill tells you to run /setup-matt-pocock-skills first, so it will not work cleanly on its own

Try asking

  • “Break this feature spec into tracer-bullet tickets with blocking edges and publish them to our tracker”
  • “Turn the plan we just discussed into local ticket files under .scratch in dependency order”
  • “Split this wide rename of the user ID column into expand, migrate and contract tickets”
  • “Create sub-issues for each slice of parent issue 123 without modifying the parent”
Step-by-step guide: how to use To TicketsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    to-tickets.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip to-tickets.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip to-tickets.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give it a clear spec or conversation first, and review the proposed ticket list carefully before approving, since blocking edges are the most error-prone part
  • Confirm which tracker is configured before running so tickets land in the right place, and check the ready-for-agent label is what you want
  • Reference an existing issue by number or URL so sub-issues link back to the parent correctly

What's inside

  • agents/openai.yaml
  • SKILL.md

Redistributed unmodified from mattpocock/skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.