to-tickets

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill to-tickets-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/MSC72m/DevForge/tree/main/skills/to-tickets
Command: npx skills add https://github.com/MSC72m/DevForge --skill to-tickets-msc72m

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 fresh 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, or similar trackers. - Expand-Contract Sequencing: Handles wide refactors (renames, retypes with large blast radius) as expand, batched migrate, and contract ticket sequences instead of forcing them into vertical slices. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it quizzes you on granularity and dependencies, then publishes one issue per ticket in dependency order with a 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 for AI agents?▼

Provide the spec or plan in conversation and the skill drafts tracer-bullet tickets, each a complete vertical slice with blocking edges. It quizzes you on granularity and dependencies, then publishes one issue per ticket in dependency order.

What is a tracer-bullet ticket in software planning?▼

A tracer-bullet ticket is a narrow but complete vertical slice cutting through every layer (schema, API, UI, tests) that is demoable on its own. Each is sized to fit in a single fresh context window so an agent can complete it independently.

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

Yes, the skill publishes to whatever tracker was configured via /setup-matt-pocock-skills. Real trackers get native blocking or sub-issue links and a ready-for-agent label; otherwise it writes one markdown file per ticket under .scratch.

How are wide refactors handled when vertical slicing fails?▼

Wide refactors with large blast radius are sequenced as expand-contract: add the new form beside the old, migrate call sites in batches sized by blast radius, then delete the old form. Each batch is its own ticket with explicit blocking edges.

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

The issue tracker and triage label vocabulary must be configured before publishing tickets. If that setup has not run, the skill cannot know where to publish or which labels to apply, so it asks you to run the setup command first.