skills.rest
SevWren
SevWrenCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

1|Updated Jun 2, 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/SevWren/Daily-Motivation-Brain-Helper --skill to-tickets-sevwren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/CLAUDE/skills/engineering/to-tickets
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill to-tickets-sevwren

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 that cannot be demoed, dependencies between tasks go undeclared, and nothing is published to a tracker. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which tickets block it, and publishes them to a local file structure or a real issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: Each ticket cuts a complete path through schema, API, UI, and tests so it is demoable on its own and fits in a single context window. - Blocking edge declaration: Every ticket lists the tickets that must complete first, 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 in conversation, ask for a ticket breakdown; the Skill proposes numbered tickets with blockers, quizzes you on granularity, then writes one file per ticket under .scratch/<feature-slug>/issues/ or creates labeled issues on your tracker. ## 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 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 vertical tracer-bullet slices, each with a title, blocking edges, and the end-to-end behavior it delivers. You review the breakdown, adjust granularity, then it publishes one ticket per file or per tracker issue in dependency order.

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

A vertical slice cuts a narrow but complete path through every layer — 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 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 via /setup-matt-pocock-skills. On a real tracker the Skill creates one issue per ticket in dependency order, uses native blocking or sub-issue relationships where available, and applies the ready-for-agent triage label.

How are large refactors handled when vertical slicing is impossible?▼

Wide refactors use expand-contract sequencing: add the new form beside the old, migrate call sites in blast-radius-sized batches as separate blocked tickets, then delete the old form last. If batches cannot stay green alone, they share an integration branch blocking a final verify ticket.

Where are local ticket files stored?▼

Local tickets are written one file per ticket under .scratch/<feature-slug>/issues/, named NN-slug.md and numbered from 01 in dependency order. Each file contains what to build, its blocked-by list, a ready-for-agent status, and acceptance criteria checkboxes.

Related Skills

Explore More Software Engineering Skills→
arxxyrarxxyr
1

to-prd

Convert conversation context and codebase understanding into a Product Requirements Document and publish it to the issue tracker.

Community
Intermediate
bobmatnycbobmatnyc

pm-ticketing-integration

Detect ticket references and enforce ticket-driven delegation across agents.

Community
Advanced
The-Vibe-CompanyThe-Vibe-Company
2.4k

to-tickets

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

Official
Intermediate
tDaliletDalile

gsd:add-todo

Add todo items with titles and metadata to a tracking list.

Community
Basic