to-tickets

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

Updated Jul 12, 2025
One-click install
npx skills add https://github.com/kpayakv2/check-products --skill to-tickets-kpayakv2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/kpayakv2/check-products/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/kpayakv2/check-products --skill to-tickets-kpayakv2

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, dependencies stay implicit, and tickets get published without clear ordering. This Skill decomposes work into vertical tracer-bullet slices, each declaring exactly which 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. - Dependency Graph Declaration: Every ticket declares its blocking edges, so the team always knows which frontier tickets can start immediately. - Flexible Publishing: Writes one local Markdown file per ticket under .scratch/<feature-slug>/issues/, or publishes native issues with blocking links and a ready-for-agent label on trackers like GitHub or Linear. - Use Case: After drafting a feature spec for a new checkout flow, run this Skill to produce a numbered set of tickets with acceptance criteria and blocking edges, then publish them to GitHub Issues in dependency order. ## 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 the conversation and invoke the Skill. It drafts vertical tracer-bullet slices, each with a title, blocking edges, and acceptance criteria, then asks you to approve the breakdown before publishing.

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

A tracer-bullet ticket is a narrow but complete vertical slice cutting through every layer (schema, API, UI, tests) so it is demoable on its own. It contrasts with horizontal slices that only cover one layer and cannot be verified independently.

Can I publish tickets to GitHub or Linear?▼

Yes, if a real issue tracker was configured via the setup Skill, tickets are published as native issues with blocking or sub-issue relationships and a ready-for-agent label. Without a tracker, they are written as local Markdown files under .scratch.

How are ticket dependencies handled?▼

Each ticket declares its blocking edges, meaning the tickets that must complete before it starts. Tickets are published in dependency order so blockers exist first, and any ticket whose blockers are done forms the workable frontier.

When should wide refactors not be vertical slices?▼

Wide refactors, like renaming a column used across the whole codebase, cannot land green as one vertical slice. The Skill sequences them as expand-contract: add the new form, migrate call sites in batches, then delete the old form.