To Tickets
Break a plan or spec into tracer-bullet tickets with explicit blocking edges
- What
- Break a plan or spec into tracer-bullet tickets with explicit blocking edges
- Cost
- Free
- Needs
- an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); run /setup-matt-pocock-skills once first so the issue tracker is configured
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the missing middle step between spec and implementation. This skill breaks a plan, spec, or the current conversation into "tracer-bullet" tickets: narrow but complete vertical cuts through every layer, 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). Distinct from mattpocock-to-spec (lot 33, synthesizing a spec) and mattpocock-implement-spec (lot 33, task graph of implementation): to-spec summarizes a spec, to-tickets turns a plan into tickets, implement-spec executes. Requires the one-time /setup-matt-pocock-skills configuration (also in this lot) so the tracker is known. Teaches the vertical-vs-horizontal slicing lesson and dependency modeling — applicable to any agentic workflow. By @mattpocock, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); run /setup-matt-pocock-skills once first so the issue tracker is configured Install "To Tickets" for me. Break a plan or spec into tracer-bullet tickets with explicit blocking edges Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/to-tickets/SKILL.md 1. Fetch the SKILL.md file for the mattpocock-to-tickets skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-to-tickets". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.