skills.rest
ankaboot-source
ankaboot-sourceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

to-tickets

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

2|Updated Jul 25, 2026
Search Tags:#issue tracker#github issues#task decomposition#agile planning#dependency graph#vertical slice#ticket breakdown
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill to-tickets-ankaboot-source
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/to-tickets
Command: npx skills add https://github.com/ankaboot-source/boucle --skill to-tickets-ankaboot-source

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 too coarse, dependencies get missed, 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 tracker. ## Core Features & Use Cases - Vertical slice breakdown: Splits work into tracer-bullet tickets that cut through every layer (schema, API, UI, tests) so each ticket is independently demoable and fits in a single context window. - Dependency graph declaration: Each ticket declares its blocking edges, published as text in local per-ticket files or as native blocking links on a real tracker like GitHub or Linear. - Self-review before publishing: In CI mode, validates granularity, blocking edges, and merge/split decisions before writing anything. - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green. - Use Case: After drafting a feature spec, invoke this Skill to produce a numbered set of agent-ready tickets under .scratch/<feature-slug>/issues/ or as labeled issues on GitHub, ordered so blockers come first. ## Quick Start Ask the agent 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 for an issue tracker?▼

Provide the spec or plan in conversation and invoke the Skill. It drafts vertical tracer-bullet slices, self-reviews granularity and dependencies, then publishes one ticket per slice to your configured tracker with blocking links and acceptance criteria.

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 — rather than covering one horizontal layer. Each completed slice is demoable or verifiable on its own and sized to fit a single fresh context window.

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

Yes. The tracker is configured by the setup step. With a real tracker, the Skill creates one issue per ticket using native blocking or sub-issue relationships and applies the ready-for-agent label; otherwise it writes one Markdown file per ticket under .scratch.

How are ticket dependencies and blocking order handled?▼

Each ticket declares the tickets that block it, and publishing happens in dependency order so blockers exist first. Tickets with no blockers can start immediately, and the workable frontier is any ticket whose blockers are all done.

When should a wide refactor not be split into vertical slices?▼

When one mechanical change, like renaming a shared symbol, breaks thousands of call sites at once, no vertical slice can land green. The Skill sequences it as expand, batched migrate, then contract, with each step as its own blocked ticket.

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
MaxWolf-01MaxWolf-01
3

to-tickets

Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.

Community
Advanced
darkmatterdarkmatter
1

improve-codebase-architecture

Detect shallow modules and propose deepening refactors using project glossary and ADRs.

Official
Advanced
jacksonlee-twjacksonlee-tw

planning-and-task-breakdown

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

Community
Intermediate