to-tickets

Breaks plans and specs into tracer-bullet tickets with declared blocking edges published to a tracker.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/kashman001/ai-workspace-template --skill to-tickets-kashman001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/kashman001/ai-workspace-template/tree/main/skills/to-tickets
Command: npx skills add https://github.com/kashman001/ai-workspace-template --skill to-tickets-kashman001

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 lack clear acceptance criteria. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which tickets block it, and publishes them to your configured issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: Splits work into narrow end-to-end slices spanning schema, API, UI, and tests, each demoable on its own and sized for a single context window. - Dependency graph declaration: Every ticket declares its blocking edges, 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 ticket chains so CI stays green batch to batch. - 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 in dependency order with a ready-for-agent triage label. ## Quick Start Ask the agent to break the current plan or a referenced 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?▼

Provide the spec path, issue number, or URL as an argument and the skill drafts vertical tracer-bullet slices, each with a title, blocking edges, and acceptance criteria. You review the numbered breakdown and approve it before anything is published.

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 — so the finished ticket is demoable on its own. Each slice is sized to fit in a single fresh context window, unlike horizontal slices that cover only one layer.

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

Yes, the skill supports both local markdown files 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; locally it writes one file per ticket in dependency order.

How are ticket dependencies and blocking edges handled?▼

Each ticket declares which other tickets must complete before it can start, and tickets are published in dependency order so blockers exist first. Tickets with no blockers can start immediately, and work proceeds along the frontier of unblocked tickets.

How does it handle large refactors that break vertical slicing?▼

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 blocked by the expand step, keeping CI green throughout.