to-tickets

Breaks plans or specs into tracer-bullet tickets with declared blocking edges published to a tracker.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/richard-jh-mccrae/PokemonAI --skill to-tickets-richard-jh-mccrae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/richard-jh-mccrae/PokemonAI/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/richard-jh-mccrae/PokemonAI --skill to-tickets-richard-jh-mccrae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or conversation into actionable work items is tedious and error-prone, especially when dependencies between tasks must be tracked. This Skill decomposes the work into tracer-bullet tickets, each declaring its blocking edges, and publishes them to your configured issue tracker. ## Core Features & Use Cases - Ticket Decomposition: Splits a plan, spec, or the current conversation into a set of tracer-bullet tickets that each deliver a thin end-to-end slice of work. - Dependency Declaration: Every ticket declares its blocking edges, either as text in one local file per ticket or as native blocking links on a real tracker. - Tracker Publishing: Publishes the resulting tickets to the configured tracker so the team can start work immediately. - Use Case: After drafting a feature spec in a conversation, ask the agent to convert it into tickets; you receive one file per ticket locally or linked issues on your tracker, each with its blocking relationships recorded. ## Quick Start Ask the agent to break the current plan or spec into tracer-bullet tickets with their blocking edges and publish them to the configured tracker.

Frequently Asked Questions about to-tickets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a plan or spec into tickets?▼

Provide the plan, spec, or current conversation to the skill and it decomposes the work into tracer-bullet tickets. Each ticket declares its blocking edges and is published to your configured tracker or written as one local file per ticket.

What is a tracer-bullet ticket?▼

A tracer-bullet ticket is a thin end-to-end slice of work that exercises the full path of a feature rather than a single layer. This skill generates such tickets from a plan or spec, each with its blocking dependencies declared.

Can I publish tickets to a real issue tracker?▼

Yes, the skill publishes tickets to the configured tracker using native blocking links for dependencies. Without a tracker, it falls back to writing one local file per ticket with blocking edges recorded as text.

How are ticket dependencies represented?▼

Dependencies are represented as blocking edges on each ticket. On a real tracker they become native blocking links; locally they are written as text inside the individual ticket file.

What inputs does the ticket breakdown accept?▼

The skill accepts a plan, a spec, or the current conversation as input. It derives the ticket set and their blocking relationships from whichever source you provide.