skills.rest
marjorg
marjorgCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-tickets

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

1|Updated Mar 2, 2025
Search Tags:#planning#github#issue tracker#task decomposition#linear#tickets#vertical slice
One-click install
npx skills add https://github.com/marjorg/setup --skill to-tickets-marjorg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/to-tickets
Command: npx skills add https://github.com/marjorg/setup --skill to-tickets-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is error-prone: slices end up horizontal, dependencies stay implicit, and tickets land in the tracker without clear ordering. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which other tickets block it, and publishes them to your configured tracker. ## Core Features & Use Cases - Vertical slice decomposition: 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. - Blocking edge modeling: Every ticket declares the tickets that gate it, published 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 batches so CI stays green between steps. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it proposes a numbered breakdown with blocking edges, quizzes you on granularity, then publishes one issue per ticket 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?▼

Provide the spec path, issue number, or work from the current conversation, and the Skill drafts vertical tracer-bullet slices. Each ticket cuts through all layers, declares its blocking tickets, and is published to your configured tracker after you approve the breakdown.

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

A vertical slice is a narrow but complete path through every layer of the stack, such as 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 a single context window.

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

Yes, the Skill supports both local markdown files under .scratch and real issue trackers like GitHub or Linear. On a real tracker it uses native blocking or sub-issue relationships and applies the ready-for-agent triage label.

How are ticket dependencies and blocking edges handled?▼

Each ticket declares which other tickets must complete before it can start. Tickets are published in dependency order so blocking edges reference real identifiers, and work proceeds on the frontier of tickets whose blockers are all done.

How does it handle large refactors that cannot be vertically sliced?▼

Wide refactors 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 blocking edges keeping CI green.

Related Skills

Explore More Software Engineering Skills→
filippolmtfilippolmt
1

to-spec

Synthesizes the current conversation into a structured spec and publishes it to the project issue tracker.

Community
Intermediate
mambo-wangmambo-wang
3

to-tickets

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

Community
Intermediate
kos3nzkos3nz

improve-codebase-architecture

Analyze domain language and ADRs to identify codebase deepening opportunities.

Community
Advanced
jacksonlee-twjacksonlee-tw

planning-and-task-breakdown

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

Community
Intermediate