{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "mattpocock-skills--split-a-plan-into-blocking-tickets",
 "repo": "mattpocock/skills",
 "repo_url": "https://github.com/mattpocock/skills",
 "repo_slug": "mattpocock-skills",
 "title": "Split a plan into tracer-bullet tickets with blockers",
 "page_title": "How to split a plan into tracer-bullet tickets with blockers with Skills",
 "summary": "Turn a conversation into a spec, then into ordered tickets that declare what blocks what.",
 "who": "A tech lead or solo developer with a big feature idea who needs work broken into pieces an agent can pick up.",
 "problem": "Large changes stall when the work is not sliced, and agents lose track of what must finish first.",
 "outcome": "A published spec and a set of tracer-bullet tickets, each with its blocking edges, in your tracker or a local file.",
 "steps": [
  "Install the plugin in Codex with `codex plugin marketplace add mattpocock/skills`, then run `codex plugin add mattpocock-skills@mattpocock`.",
  "Run `/setup-matt-pocock-skills` once in the repo and choose your issue tracker or local files.",
  "Discuss the feature with the agent, then run `/to-spec` to publish the spec from the conversation.",
  "Run `/to-tickets` on the spec and pick either local text files or native blocking links on your tracker."
 ],
 "agent_prompt": "In the mattpocock/skills repo, use to-spec on our current discussion about <feature>, then use to-tickets to split the spec into tracer-bullet tickets. Expected output: a published spec and a ticket list where each ticket names its blocking tickets. Verify that no ticket is blocked by a ticket that depends on it.",
 "agents": [
  "codex",
  "claude-code"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "Native blocking links are only available when you use a real tracker; with local files the blocking edges are written as text.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "shell",
 "requirements": [
  "A coding agent that supports the plugin or skills install route, such as Claude Code or Codex",
  "A project repository the agent can read and edit",
  "Optional: an issue tracker such as GitHub or GitLab, or a local folder for tickets"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/mattpocock-skills/split-a-plan-into-blocking-tickets/",
 "md": "https://dedupedai.com/use-cases/mattpocock-skills/split-a-plan-into-blocking-tickets/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/mattpocock-skills--split-a-plan-into-blocking-tickets.json",
 "api_version": "v1"
}