skills.rest
Ab0umar
Ab0umarCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

Updated Sep 19, 2026
Search Tags:#issue tracker#sprint planning#github issues#task decomposition#dependency graph#vertical slice#ticket breakdown
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill to-tickets-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill to-tickets-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up as horizontal layer-by-layer chunks that cannot be demoed, dependencies between tasks go undeclared, and nothing is published to a tracker. This Skill converts planning material into vertical-slice tickets with explicit blocking edges, ready for agents or developers to pick up. ## Core Features & Use Cases - Tracer-bullet slicing: Drafts tickets that each cut a complete path through schema, API, UI, and tests, so every ticket is independently demoable and sized for a single context window. - Dependency modeling: Assigns blocking edges to every ticket and orders publication blockers-first, including expand-contract sequencing for wide refactors that cannot land as vertical slices. - Tracker publishing: Writes one local Markdown file per ticket under .scratch/<feature-slug>/issues/ or publishes native issues with blocking links and a ready-for-agent triage label on GitHub, Linear, or similar trackers. - Use Case: After finalizing a feature spec for a patient portal, ask the agent to break it into tickets; it proposes a numbered breakdown with blocking edges, quizzes you on granularity, then publishes the approved set to your configured tracker. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets and publish them to the configured issue 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 for an issue tracker?▼

Provide the spec path, issue URL, or existing conversation context and ask for a ticket breakdown. The Skill drafts vertical slices with blocking edges, quizzes you on granularity, then publishes the approved tickets to your configured tracker.

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, tests) rather than a horizontal chunk of one layer. Each completed slice is demoable or verifiable on its own and sized to fit a single context window.

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

Yes, the Skill supports both. Local mode writes one Markdown file per ticket under .scratch/<feature-slug>/issues/, while a real tracker gets native issues with blocking links and a ready-for-agent triage label.

How are ticket dependencies and blocking edges handled?▼

Each ticket declares which other tickets block it, and tickets are published in dependency order so edges reference real identifiers. Wide refactors use expand-contract sequencing: add the new form, migrate call sites in batches, then delete the old form.

Why does the Skill say to run setup-matt-pocock-skills?▼

The Skill requires a configured issue tracker and triage label vocabulary before publishing. If that configuration is missing, it instructs you to run /setup-matt-pocock-skills to provide it.

Related Skills

Explore More Software Engineering Skills→
PVMalovePVMalove

to-spec

Synthesizes conversation context into a specification and publishes it as a GitHub epic issue.

Community
Intermediate
IsKenKenYaIsKenKenYa
2

wayfinder

Plans large efforts as decision-ticket maps on an issue tracker.

Community
Advanced
darkmatterdarkmatter
1

improve-codebase-architecture

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

Official
Advanced
SanHsienSanHsien
1

planning-and-task-breakdown

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

Community
Intermediate