skills.rest
damoke012
damoke012COMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

Updated Apr 16, 2025
Search Tags:#planning#github#issue tracker#dependency graph#vertical slice#tracer bullet#ticket breakdown
One-click install
npx skills add https://github.com/damoke012/eks_code --skill to-tickets-damoke012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/damoke012/eks_code/tree/main/.claude-env/skills/to-tickets
Command: npx skills add https://github.com/damoke012/eks_code --skill to-tickets-damoke012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: slices are often cut horizontally by layer, dependencies between tasks go undeclared, and tickets end up too big for a single work session. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to your configured tracker. ## Core Features & Use Cases - Vertical slice breakdown: Each ticket cuts a complete path through schema, API, UI, and tests so it is demoable on its own and fits in a single fresh context window. - Dependency graph declaration: Every ticket declares which other tickets block it, so work can proceed along the unblocked frontier. - Wide refactor handling: Mechanical changes with large blast radius are sequenced as expand-migrate-contract instead of being forced into a tracer bullet. - Dual publishing targets: Writes one Markdown file per ticket under .scratch/<feature-slug>/issues/ locally, or creates native issues with blocking links and a ready-for-agent label on GitHub, Linear, or similar trackers. - Use Case: After drafting a feature spec in conversation, ask for a ticket breakdown; the Skill proposes numbered tickets with blockers, quizzes you on granularity, then publishes the approved set to your tracker. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets with 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 feature spec into tickets?▼

Provide the spec or plan in conversation and ask for a ticket breakdown. The Skill drafts vertical tracer-bullet slices, shows each ticket's title, blockers, and delivered behavior, then iterates with you until you approve the breakdown.

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

A vertical slice cuts a narrow but complete path 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 a single fresh context window.

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

Yes, if a real issue tracker was configured via the setup skill, tickets are published as native issues with the platform's blocking or sub-issue relationships and a ready-for-agent label. Otherwise one Markdown file per ticket is written under .scratch/<feature-slug>/issues/.

How are dependencies between tickets handled?▼

Each ticket declares its blocking edges, meaning the tickets that must complete before it can start. Tickets are published in dependency order so blockers exist first, and work proceeds along the frontier of tickets whose blockers are all done.

When should a wide refactor not be a vertical slice?▼

When one mechanical change, like renaming a column, breaks thousands of call sites at once so no vertical slice can land green. The Skill sequences it as expand-contract: add the new form, migrate call sites in batches, then delete the old form.

Related Skills

Explore More Software Engineering Skills→
Ab0umarAb0umar

to-spec

Synthesizes conversation context into a structured spec published to the project issue tracker.

Community
Intermediate
The-Vibe-CompanyThe-Vibe-Company
2.4k

to-tickets

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

Official
Intermediate
darkmatterdarkmatter
1

improve-codebase-architecture

Detect shallow modules and propose deepening refactors using project glossary and ADRs.

Official
Advanced
jacksonlee-twjacksonlee-tw

planning-and-task-breakdown

Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.

Community
Intermediate