to-tickets

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

Updated Feb 22, 2024
One-click install
npx skills add https://github.com/tlipoca9/dotfiles --skill to-tickets-tlipoca9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/to-tickets
Command: npx skills add https://github.com/tlipoca9/dotfiles --skill to-tickets-tlipoca9

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, horizontally sliced by layer, or missing dependency information, so agents and developers cannot pick up work independently. ## Core Features & Use Cases - Vertical Slice Breakdown: Splits work into tracer-bullet tickets that each cut a complete path through schema, API, UI, and tests, sized to fit a single context window. - Blocking Edge Declaration: Every ticket declares which other tickets block it, published as text edges in local per-ticket files or as native blocking links on GitHub, Linear, and similar trackers. - Wide Refactor Sequencing: Handles codebase-wide mechanical changes via expand-migrate-contract ticket sequences that keep CI green batch to batch. - Use Case: After drafting a feature spec, ask for a ticket breakdown; review the proposed numbered list with blocking edges, iterate on granularity, then publish one issue per ticket to your tracker with the ready-for-agent label. ## Quick Start Ask the AI to break the current plan or spec into tracer-bullet tickets with blocking dependencies 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 AI agents?▼

Provide the spec or plan in conversation and request a ticket breakdown. The skill drafts vertical slices that each deliver end-to-end behavior, quizzes you on granularity and blocking edges, then publishes 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, including schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own and sized for a single context window.

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

Yes, the skill supports both targets configured via /setup-matt-pocock-skills. Real trackers get one issue per ticket with native blocking or sub-issue links, while local mode writes one Markdown file per ticket under .scratch with text-based blocking edges.

How are wide refactors handled when vertical slicing fails?▼

Wide refactors use expand-contract sequencing: first add the new form beside the old, then migrate call sites in blast-radius-sized batches as separate tickets, and finally delete the old form. Each batch keeps CI green because the old form still exists.

What happens if the issue tracker is not configured?▼

The skill expects the tracker and triage label vocabulary to be provided beforehand. If they are missing, it instructs you to run /setup-matt-pocock-skills before proceeding with ticket publication.