to-tickets
An agent skill by mattpocock, from mattpocock/skills. Tags: issue-tracking, planning, project-management, tracking, workflow.
What it does
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add mattpocock/skills --skill to-tickets
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/mattpocock/skills
cp -r skills/skills/engineering/to-tickets ~/.claude/skills/to-tickets
Safety box score
Grade B, low risk: 18 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill turns a plan, spec, or conversation into tracker tickets and can either write them to local `.scratch` files or publish them to a configured issue tracker. The main blast radius is persistent issue creation and the possibility of sending plan/spec content to a remote tracker; it does not ship code execution or privilege-escalation machinery.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 0 (none) | No shell commands, code evaluation, or native scripts are present; the skill is only markdown guidance plus a YAML config. |
| Network access | 2 (moderate) | It can fetch referenced issue/spec URLs ('fetch it and read its full body and comments') and later publish tickets to the configured tracker. |
| Filesystem reach | 1 (low) | Local mode writes one file per ticket under `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, but that stays within the working tree. |
| Secrets & credentials | 0 (none) | There is no handling of tokens, passwords, keychains, `.env` files, or other credential stores. |
| Privilege & persistence | 0 (none) | No sudo, global installs, services, shell startup edits, or OS-setting changes are requested. |
| Instruction hijack surface | 0 (none) | The skill does not tell the agent to ignore higher-priority instructions or hide behavior; it only defines a bounded workflow. |
| Irreversible actions | 2 (moderate) | It creates and publishes tracker issues and blocking edges after approval ('Publish the approved tickets'; 'apply the `ready-for-agent` triage label'). |
| Transparency | 0 (none) | The shipped files are readable markdown/YAML; there are no binaries, decoded blobs, or hidden runtime downloads. |
Before installing
- Confirm whether `/setup-matt-pocock-skills` is configured for a local `.scratch` tracker or a real remote issue tracker.
- Review any spec/issue URL you plan to pass in; the skill will fetch the full body and comments.
- Decide whether ticket text may expose sensitive roadmap or product details before letting it publish.
Rated 2026-10-20 by an automated review of 2 files from the skill's repository.
Source
- Repository
- mattpocock/skills (all skills from this repository)
- Path
- skills/engineering/to-tickets/SKILL.md
- Branch
- main
- Updated
- 2026-10-05
Related skills
- to-spec — Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
- triage — Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
- wayfinder — Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker.
- new-unity-project — Use when starting a brand-new Unity game or project from scratch — "make/start/create a new game", "bootstrap a Unity project".
- events — When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops.
- expo-project-structure — Framework (OSS). Folder structure for a new Expo app.