Verified:GitHub

to-tickets

Breaks plans and specs into tracer-bullet tickets with declared blocking dependencies.

1|Updated Jul 2, 2026

Search Tags:#planning #issue tracker #github issues #dependency graph #vertical slice #tracer bullet #ticket decomposition

One-click install

npx skills add https://github.com/filippolmt/skills --skill to-tickets-filippolmt

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/filippolmt/skills/tree/main/skills/to-tickets
Command: npx skills add https://github.com/filippolmt/skills --skill to-tickets-filippolmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tickets end up as horizontal layer slices that cannot ship independently, dependencies between them go undeclared, and nothing is sized to fit a single working session. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to your tracker. ## Core Features & Use Cases - Vertical slice decomposition: Splits work into narrow but complete slices cutting through schema, API, UI, and tests, each demoable on its own and sized for one fresh context window. - Blocking edge modeling: Every ticket declares which other tickets gate it, so the workable frontier is always clear; wide refactors are sequenced as expand-migrate-contract instead of forced into a single slice. - Dual publishing targets: Writes one Markdown file per ticket under `.scratch/<feature-slug>/issues/` locally, or creates real issues with native blocking links and a `ready-for-agent` label on trackers like GitHub or Linear. - Use Case: After drafting a feature spec in conversation, invoke the Skill to get a numbered, dependency-ordered ticket breakdown, refine granularity through a quick review quiz, then publish the approved set to GitHub Issues ready for agent pickup. ## Quick Start Ask the assistant to break the current plan or a referenced spec into tracer-bullet tickets with blocking dependencies 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

Why should tickets avoid file paths and code snippets?▼

File paths and code go stale quickly as the codebase evolves, making tickets misleading. The exception is prototype snippets that encode a decision — a state machine, schema, or type shape — which may be inlined with a note about their origin.