← All skills · Automation · Ticket Splitter

Runs inClaude Code Codex Cursor

Muse

Dot Grok Bot

Cue OpenClaw

Hermes

Install guidesClaude Code Codex Cursor Muse

Needs:Your written spec: spec.txt (Spec and Goal lines, then one Item line per piece of work — id | title | size S, M, or L — one Check line per acceptance check — item id | check text — and one After line per dependency — ticket | waits-for).

Automation Premium

Ticket Splitter

Turn one spec into small tickets with acceptance checks and dependency order: each ticket sized S, M, or L, each check tied to the ticket it proves, and the board sorted so no ticket appears before something it depends on.

Version 1.0.0

Subscribe — All Skills, one subscription.No exclusions. Curated, verified, and continuously updated.

Get this Skill with Premium See plans

Reads one plain-text file you write — spec.txt, with a Spec line and a Goal line, plus Item lines (id | title | size S, M, or L), Check lines (item id | acceptance check), and After lines (ticket | waits-for) — and produces tickets.md: the spec and goal first, then the work-order table (tickets sorted by dependency depth, then by size S before M before L, then by id), then the acceptance checks per ticket as unchecked boxes. Order is a build sequence, not a schedule: depth 0 has no dependencies and goes first, and a ticket's depth is one more than the deepest ticket it waits for. Local-only, standard library only; a check or dependency naming an item that was never listed is dropped and named, a dependency that would close a cycle is dropped and named, and a ticket with no acceptance checks is listed as incomplete — the board is a document, it files nothing in any tracker and assigns work to no one.

Good fit Breaking a finished spec into small tickets you can work top-down Seeing which tickets are still unscoped because they have no checks Handing a board to someone else with the build order already decided

Similar Skills

Premium

Email Triage Automation

Read full threads
Sort into 3 buckets
Draft in your voice
Approve & send

Premium

Smart Scheduling Automation

Gather constraints
Check all calendars
Offer local times
Hold or invite

Free

Deadline-Driven Follow-Up

Capture the cutoff
Watch for stalls
Nudge at 3 points
Close the loop

Premium

Durable Bulk Execution

Shard the list
Checkpoint each item
Idempotent runs
Verify completion

View all skills →

What you get

A work-order table sorted by dependency depth, then by size, then by id
Every acceptance check listed as an unchecked box under its ticket
Each ticket's size and what it waits for, visible at a glance
Every gap, input error, and warning named in the report

Good fit

Breaking a finished spec into small tickets you can work top-down
Seeing which tickets are still unscoped because they have no checks
Handing a board to someone else with the build order already decided

Not for

Estimating how long anything takes — order is a sequence, not a schedule
Proving quality — a checked box means you verified one behaviour, not that it is tested or reviewed
Filing tickets in a tracker or assigning work — the board is a document, not a queue

Sample output

An example of what this Skill produces. Sample content, shown for illustration.

Ticket Splitter report — sample

Tickets: 4 | With checks: 4 | Without checks: 0 | Dependencies: 3 | Gaps: 0 | Errors: 0 | Warnings: 0

Work order: T1 Email link request form (S, 2 checks) → T2 Verify endpoint + session cookie (M, after T1, 2 checks) → T3 Paid download button on skill pages (S, after T2, 1 check) → T4 Expired-link error page (S, after T2, 1 check).

Gaps: none.

About this Skill

You say

Turn this spec into a ticket board — small tickets with acceptance checks, in dependency order.

How to install

Copy the install prompt into your agent: Read https://skillu.dev/install/agent.md, then install the Ticket Splitter skill (ticket-splitter).
Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
Call it with a slash command, e.g. /ticket-splitter, and describe what you want in plain words.

FAQ

How is the work order decided?

From the dependencies you list, nothing else: depth 0 has no dependencies and goes first, and a ticket's depth is one more than the deepest ticket it waits for, so a ticket never appears before something it depends on. Within one depth, S comes before M before L, then by id. A dependency that would close a cycle is dropped and named.

What happens to a ticket with no acceptance checks?

It stays on the board and is listed as incomplete, with a gap naming how many tickets have no checks — a ticket you cannot check is not done, it is unscoped. Add Check lines for it and re-run; the board only counts checks you wrote.

Get Premium access Browse more skills