skills.rest
inkfin
inkfinCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

Breaks plans and specs into tracer-bullet ticket files with blocking dependencies under plans/.

Updated Jan 19, 2023
Search Tags:#markdown#task planning#dependency tracking#vertical slice#spec decomposition#tracer bullet#ticket breakdown
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill to-tickets-inkfin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_to-tickets
Command: npx skills add https://github.com/inkfin/dotfiles --skill to-tickets-inkfin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan or spec into actionable work often produces either one giant task or a pile of unordered items with no clear dependencies. This Skill converts a plan, spec, or conversation into a set of small, independently demoable tickets, each declaring which other tickets block it, stored as local markdown files. ## Core Features & Use Cases - Vertical slice breakdown: Splits work into tracer-bullet tickets that cut through every layer (schema, API, UI, tests) so each ticket is demoable on its own and fits in a single context window. - Dependency tracking: Each ticket file declares its blocking edges, so you always know which tickets are ready to work (the frontier) and which are gated. - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green batch to batch. - Use Case: After drafting a feature spec, ask for a ticket breakdown; the Skill proposes numbered tickets with blockers, quizzes you on granularity, then writes one file per ticket under plans/<feature-slug>/issues/. ## Quick Start Ask the agent to break the current plan or spec into tracer-bullet tickets with blocking dependencies and write them as files under plans/.

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 small tickets?▼

Provide the spec or plan in conversation and ask for a ticket breakdown. The Skill drafts vertical slices that each deliver end-to-end behavior, quizzes you on granularity and dependencies, then writes one markdown file per ticket under plans/.

What is a tracer-bullet or vertical slice ticket?▼

A vertical slice ticket cuts a narrow but complete path through every layer — schema, API, UI, and tests — rather than covering one horizontal layer. Each completed slice is demoable or verifiable on its own and sized to fit a single context window.

How are ticket dependencies tracked in local markdown files?▼

Each ticket file under plans/<feature-slug>/issues/ lists its blocking tickets by number and title in a Blocked by field. Tickets with no blockers can start immediately, and you work the frontier of tickets whose blockers are all done.

How should wide refactors be split into tickets?▼

Wide refactors use expand-contract sequencing instead of vertical slicing: first add the new form beside the old, then migrate call sites in batches sized by blast radius, and finally delete the old form in a ticket blocked by every migration batch.

When should I not use vertical slice ticket breakdown?▼

Avoid forcing vertical slices on mechanical changes whose blast radius spans the whole codebase, such as renaming a shared symbol, since no single slice can land green. Use expand-contract batching with an integration branch instead.

Related Skills

Explore More Software Engineering Skills→
MoofonLiMoofonLi
2

to-spec

Synthesizes conversation context into a structured spec document committed to the repository.

Community
Intermediate
MaxWolf-01MaxWolf-01
3

to-tickets

Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.

Community
Advanced
J0JngJ0Jng
7

to-tickets

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

Community
Intermediate
prestariusprestarius
1

to-issues

Convert plans or backlogs into independent tracker issues with acceptance criteria.

Community
Intermediate