to-tickets

Splits a slice-ready spec into independent vertical-slice work-units with a dependency board.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill to-tickets-konstantinos-malavazos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/to-tickets
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill to-tickets-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large tickets that span multiple layers and repos are hard to parallelize safely. This Skill decomposes a slice-ready specification into independent, vertically complete work-units so each slice can be built and verified on its own testing seam without stepping on the others. ## Core Features & Use Cases - Vertical slice decomposition: Turns behaviors from a spec into thin, complete slices that cross every layer of the repo's chain, rejecting single-layer slices that prove nothing. - Dependency DAG and wave board: Renders a slice-board.md with parallel waves, a Mermaid dependency graph, and per-slice cards showing lanes, repos, and verify seams. - Deferral-aware lanes: Classifies slices as READY, DEFERRED REGION (with fail-loud stubs), or PARKED based on open questions priced by the grilling gate, so unresolved decisions never silently corrupt the plan. - Use Case: During a /start-ticket decompose run, after /to-spec writes slice-spec.md, run this Skill to produce slice work-unit files and an approval board, then approve it so the orchestrator dispatches slices into worktrees. ## Quick Start Run the to-tickets skill on the current ticket after /to-spec has produced slice-spec.md, then review and approve the generated slice board.

Frequently Asked Questions about to-tickets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a large ticket into parallel work slices?

Run this Skill after /to-spec produces slice-spec.md. It drafts one vertical slice per behavior, computes blocked-by edges as a DAG, writes one work-unit file per slice under handoffs/<TICKET-ID>/slices/, and renders an approval board you accept or edit before dispatch.

What makes a valid vertical slice in ticket decomposition?

A valid slice is a thin, complete path through every layer of the repo's chain that the behavior needs, verifiable on its own testing seam. A single layer, such as only the schema change, is rejected because it has no observable result to demonstrate.

Does this Skill create issues in Jira or another tracker?

No. Slices are internal work-unit files only, and one ticket ID remains one ticket in the tracker. The Skill never writes to the tracker or to memory; it only writes files under the handoffs directory.

What happens to slices blocked by unanswered questions?

Slices are assigned lanes based on deferral pricing. DEFERRED REGION slices ship with fail-loud stubs and deferred criteria, while PARKED slices get no work-unit file at all and are promoted later by the planner during RE-PLAN via /resume-ticket.

When should the decompose path fall back to sequential execution?

If the analysis shows there is really only one slice, the ticket should not have entered the decompose path. The Skill reports this so the orchestrator falls back to the sequential pipeline, and nothing written needs undoing.