skills.rest
julianckt
juliancktCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tickets end up as horizontal layer slices, dependencies stay implicit, and nothing is sized to fit a single working session. This Skill decomposes work into vertical tracer-bullet tickets, each declaring exactly which other tickets block it, 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 one fresh context window. - Explicit dependency graph: Every ticket declares its blocking edges, published as text in local per-ticket files or as native blocking links on GitHub, Linear, or similar trackers. - Wide refactor handling: Large mechanical changes are sequenced as expand-migrate-contract batches instead of being forced into a single slice. - Use Case: After drafting a feature spec, ask for a ticket breakdown; review the proposed titles, blocking edges, and deliverables, approve the plan, and have one issue per ticket published with a ready-for-agent label. ## Quick Start Ask the agent to break the current plan or spec into tracer-bullet tickets with blocking dependencies 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 the Skill drafts tracer-bullet tickets, each a vertical slice through schema, API, UI, and tests. You review the numbered breakdown, adjust granularity and blocking edges, then approve it for publishing.

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

A vertical slice ticket cuts a narrow but complete path through every layer of the stack so it is demoable or verifiable on its own. It contrasts with horizontal slices that cover only one layer and cannot be demonstrated independently.

Can I publish tickets to GitHub or Linear?▼

Yes, the Skill publishes one issue per ticket in dependency order using the tracker's native blocking or sub-issue relationships where available. Without a real tracker, it writes one local Markdown file per ticket under a .scratch directory instead.

How are ticket dependencies and blocking edges handled?▼

Each ticket declares which other tickets must complete before it can start, and tickets are published blockers-first so edges reference real identifiers. Locally, edges appear as text in each ticket file; on a tracker, they become native blocking links.

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

A wide refactor, such as renaming a column used across the whole codebase, cannot land green as one slice. 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 Product & Management Skills→
fworks-techfworks-tech
2

the-architect

Produce specs, task decompositions, and ADRs before coding.

Community
Advanced
IsKenKenYaIsKenKenYa
2

wayfinder

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

Community
Advanced
TimothyNguyen04TimothyNguyen04

create-tickets

Generate engineering tickets from PRDs with acceptance criteria and estimates.

Community
Advanced
SanHsienSanHsien
1

planning-and-task-breakdown

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

Community
Intermediate