skills.rest
jwh3times
jwh3timesCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

1|Updated Oct 29, 2025
Search Tags:#planning#issue tracker#github issues#dependency graph#vertical slicing#tracer bullet#ticket breakdown
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill to-tickets-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/jwh3times/holland-vip --skill to-tickets-jwh3times

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 land in the tracker without clear ordering. This Skill decomposes work into vertical tracer-bullet slices, each explicitly declaring which tickets block it, and publishes them to your configured tracker. ## Core Features & Use Cases - Vertical slice breakdown: 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. - Dependency modeling: Assigns blocking edges to every ticket and publishes them as text references in local files or as 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, iterates with you on granularity, then publishes one issue per ticket in dependency order with the 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 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 with dependencies?▼

Pass the spec path or issue reference to the skill, which drafts vertical tracer-bullet slices, assigns blocking edges to each ticket, and asks you to confirm granularity before publishing. Approved tickets are written to the configured tracker in dependency order.

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

A vertical slice is a narrow but complete path through every layer of the stack, including schema, API, UI, and tests, so the finished ticket is demoable on its own. Each slice is sized to fit in a single fresh context window.

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

Yes, the tracker is configured by running /setup-matt-pocock-skills. With a real tracker, tickets become issues using native blocking or sub-issue relationships; without one, they are written as markdown files under .scratch with text-based blocking references.

How are large refactors handled when vertical slicing does not work?▼

Wide refactors are sequenced as expand-contract: first add the new form beside the old, then migrate call sites in batches sized by blast radius, and finally delete the old form. Each phase becomes its own ticket with blocking edges so CI stays green.

Why does the skill avoid file paths and code snippets in tickets?▼

File paths and code go stale quickly as the codebase evolves, so tickets describe end-to-end behavior instead. The exception is prototype snippets that encode a decision, such as a state machine or type shape, which may be inlined with a note.

Related Skills

Explore More Product & Management Skills→
GuitarAlchemistGuitarAlchemist

to-prd

Convert conversation context into a PRD and post it to the issue tracker.

Official
Intermediate
ArcReelArcReel
4.3k

wayfinder

Plan large efforts as decision tickets tracked on an issue tracker.

Official
Advanced
mrmtsuruyamrmtsuruya

improve-codebase-architecture

Identify and propose codebase deepening opportunities to improve architecture and testability.

Community
Advanced
yashs33244yashs33244
1

to-issues

Convert plans into dependency-ordered issue tickets with acceptance criteria.

Community
Intermediate