to-tickets

Installation
SKILL.md

To Tickets

Break a plan, specification, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring the tickets that block it. Preserve its established goal throughout. Call this source the decomposition input.

Apply thinking-in-systems to preserve the goal and use the language in its references/CONTEXT.md. Let the other focused systems skills load when their descriptions match the work. Keep their guidance in its owning skill; the tickets record the resulting work.

If decomposition exposes a material decision the input did not settle, return the exact gap to planning instead of inventing an answer.

Process

1. Gather context

Work from the decomposition input and whatever is already in the conversation context. If the user passes a reference, fetch it and read its full body and comments.

Continue when one exact decomposition input and every source needed to interpret it have been read, or a material gap has been returned to planning.

2. Explore the current system (optional)

If you have not already explored the current system, do so to understand its state. For software, explore the codebase. Ticket titles and descriptions should use the project's domain vocabulary and respect accepted decision records in the affected area.

Installs
8
GitHub Stars
3
First Seen
Aug 9, 2026