skills.rest
tanqimin
tanqiminCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

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

10|3|Updated Jul 18, 2019
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/tanqimin/MyFavsORM --skill to-tickets-tanqimin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/to-tickets
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill to-tickets-tanqimin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan or spec into actionable work items is hard: tasks end up as horizontal layer slices that cannot be demoed, dependencies between tasks go undeclared, and tickets get published to trackers inconsistently. This Skill converts a plan, spec, or conversation into a set of vertical-slice tickets, each with explicit blocking edges, and publishes them to a local file structure or a real issue tracker. ## Core Features & Use Cases - Tracer-bullet ticket breakdown: Splits work into vertical slices that cut through every layer (schema, API, UI, tests) so each ticket is independently demoable and sized for a single context window. - Dependency graph declaration: Every ticket declares which other tickets block it, published as text edges 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 between batches. - Interactive refinement: Quizzes the user on granularity, blocking edges, and merge/split decisions before publishing. - Use Case: After drafting a feature spec for a new checkout flow, run this Skill to produce six numbered tickets with acceptance criteria and blocking edges, published as GitHub issues labeled ready-for-agent. ## Quick Start Ask the assistant to break the current plan or a referenced 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 for my team?▼

Provide the spec or plan in the conversation and the Skill drafts tracer-bullet tickets, each a vertical slice with blocking edges and acceptance criteria. You review the breakdown, adjust granularity, then it publishes to your configured tracker.

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

A vertical slice cuts a narrow but complete path through every layer (schema, API, UI, tests) rather than covering one horizontal 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 publishes one issue per ticket in dependency order, using the platform's native blocking or sub-issue relationships where available. Without a tracker, it writes one markdown file per ticket under .scratch/<feature-slug>/issues/.

How are dependencies between tickets represented?▼

Each ticket declares its blocking edges: the tickets that must complete before it starts. On real trackers these become native blocking links; in local files they appear as a Blocked by list referencing ticket numbers and titles.

How does it handle large refactors that break many call sites?▼

Wide refactors are sequenced as expand-contract: add the new form beside the old, migrate call sites in blast-radius-sized batches as separate blocked tickets, then delete the old form in a final ticket blocked by every migration batch.

When should I not use vertical slice ticket breakdown?▼

Avoid forcing wide mechanical refactors (renames, shared type changes) into tracer bullets, since no vertical slice lands green. Use the expand-contract sequencing instead, and run the setup command first if no tracker is configured.

Related Skills

Explore More Product & Management Skills→
AnasIsmai1AnasIsmai1

to-issues

Break plans and PRDs into vertical-slice issues on a project issue tracker.

Community
Intermediate
IsKenKenYaIsKenKenYa
2

wayfinder

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

Community
Advanced
kos3nzkos3nz

improve-codebase-architecture

Analyze domain language and ADRs to identify codebase deepening opportunities.

Community
Advanced
jgaborjgabor
3

planera

Create structured PLAN.md files with tasks, constraints, and acceptance criteria.

Community
Advanced