skills.rest
falentio
falentioCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

Updated Aug 22, 2026
Search Tags:#issue tracker#sprint planning#github issues#dependency graph#vertical slice#tracer bullet#ticket decomposition
One-click install
npx skills add https://github.com/falentio/cimi --skill to-tickets-falentio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/to-tickets
Command: npx skills add https://github.com/falentio/cimi --skill to-tickets-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up as horizontal layer-by-layer slices that cannot be demoed, dependencies between tasks go undeclared, and tickets get published to a tracker in the wrong order. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to a local file store or a real issue 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 which other tickets block it, so work can proceed along the unblocked frontier. - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green batch to batch. - Dual publishing targets: Writes one Markdown file per ticket under .scratch/<feature-slug>/issues/ locally, or creates 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 analytics dashboard, run this Skill to produce six ordered tickets where the schema ticket blocks the API ticket, which blocks the UI ticket, then publish them to GitHub with native blocking links. ## Quick Start Ask the assistant to break the current plan or a referenced spec into tracer-bullet tickets with blocking edges 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 tracer-bullet tickets, each a complete vertical slice through schema, API, UI, and tests. You review the proposed breakdown, adjust granularity and blocking edges, then approve it for publishing.

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

A vertical slice ticket cuts a narrow but complete path through every layer of the stack rather than implementing one horizontal layer. Each finished 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 Skill publishes to whatever tracker was configured by the setup command. On a real tracker it creates one issue per ticket in dependency order with native blocking links and a ready-for-agent label; locally it writes one Markdown file per ticket under .scratch.

How are dependencies between tickets handled?▼

Each ticket declares its blocking edges, meaning the tickets that must complete before it can start. Tickets are published blockers-first so edges reference real identifiers, and work proceeds along 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: first add the new form beside the old, then migrate call sites in blast-radius-sized batches as separate tickets, and finally delete the old form once no callers remain. This keeps CI green between batches.

Related Skills

Explore More Product & Management Skills→
arthur-debertarthur-debert

planning

Plan a feature from loose ideas into a structured delivery workflow.

Community
Advanced
IsKenKenYaIsKenKenYa
2

wayfinder

Plans large efforts as decision-ticket maps on an issue tracker.

Community
Advanced
maggitmaggit

todo

Decompose a project into sprint-ready tasks with priorities, effort estimates, and dependencies.

Community
Intermediate
malue-aimalue-ai
36

planning-task

Generate structured task plans with dependencies in plan.json and todo.md.

Official
Intermediate