skills.rest
sndrgrdn
sndrgrdnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-tickets

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

Updated Apr 23, 2026
Search Tags:#project planning#issue tracker#github issues#dependency graph#vertical slices#tracer bullet#ticket breakdown
One-click install
npx skills add https://github.com/sndrgrdn/skills --skill to-tickets-sndrgrdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/sndrgrdn/skills/tree/main/to-tickets
Command: npx skills add https://github.com/sndrgrdn/skills --skill to-tickets-sndrgrdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up too coarse, dependencies stay implicit, and tickets get published without clear ordering. This Skill decomposes work into vertical tracer-bullet slices, each declaring which tickets block it, and publishes them to your configured 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 a single context window. - Blocking edge modeling: Every ticket declares the tickets that must complete first, published as text references in local files or native blocking links on GitHub, Linear, or similar trackers. - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract ticket chains so CI stays green batch to batch. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it proposes a numbered breakdown with blocking edges, quizzes you on granularity, then publishes one issue per ticket in dependency order with a ready-for-agent label. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets 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 feature spec into tickets?▼

Pass the spec path or issue reference to the skill, which reads the full body, optionally explores the codebase, and drafts vertical tracer-bullet slices. It presents the breakdown for your approval before publishing one ticket per slice to your configured tracker.

What is a tracer-bullet ticket in project planning?▼

A tracer-bullet ticket is a vertical slice cutting through every layer (schema, API, UI, tests) rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own and sized to fit in a single fresh context window.

Can I publish tickets to GitHub or Linear instead of local files?▼

Yes, the skill publishes to whatever tracker was configured by the setup command. On a real tracker it creates one issue per ticket using native blocking or sub-issue relationships; locally it writes one markdown file per ticket under .scratch.

How are ticket dependencies and blocking edges handled?▼

Each ticket declares the tickets that must complete before it can start. Tickets are published in dependency order so blockers exist first, and edges appear as native blocking links on real trackers or as text references in local files.

When should wide refactors not be vertical slices?▼

Wide refactors, where one mechanical change breaks thousands of call sites, cannot land green as a vertical slice. The skill sequences them as expand-migrate-contract: add the new form, migrate call sites in batches, then delete the old form.

Related Skills

Explore More Software Engineering Skills→
HaamiahphpHaamiahphp

spec-driven-implementation

Create and maintain PRODUCT.md and TECH.md specs under specs/<ticket-number>/ before implementation.

Community
Intermediate
RefractSystemsRefractSystems

planning-and-task-breakdown

Break down specifications into ordered tasks with acceptance criteria and dependencies.

Official
Intermediate
assofohdzassofohdz
25

improve-codebase-architecture

Identify shallow modules and propose deep-module refactors using domain glossaries and ADRs.

Community
Advanced
agoodwayagoodway

openspec-onboard

Guides users through a complete OpenSpec workflow cycle from task selection to archiving.

Official
Advanced