spec-to-tickets
Skill11 starsChanged 3 months agoMITView on GitHub
Turn a spec into a breakdown worth building from: prioritise and check an existing breakdown (or make a minimal one) so every slice is vertical, the first increment is a walking skeleton, every Must traces to the PRD, and each timebox keeps DSDM's MoSCoW contingency. A script checks the result; tickets go to beads, GitHub or Linear only when asked. Use for "break the spec into tickets", "prd-to-tickets", "prioritise these issues", "MoSCoW this backlog", "what do we build first", "slice this into vertical increments", and for checking a breakdown that already exists: whether its slices are horizontal, which items are Must Haves for a timebox, whether each timebox keeps contingency. Not for writing the PRD or spec (spec-ready) or a slice's implementation plan (writing-plans).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- engineering-alpina/spec-to-lineartheir own version, first seen Sep 25, 2026
- alastairlundy/skillstheir own version, first seen Jul 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- alastairlundy/skills★ 0same name
- engineering-alpina/spec-to-linear★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adr-authorSkill
- beadsSkill
- azadvertizerSkill
- business-planSkill
- c7searchSkill
- clear-and-humanSkill
- convert-to-webpSkill
- cv-and-humanSkill
- cv-cover-letterSkill
- cv-evidence-baseSkill
- dev-fleetSkill
- excalidraw-diagramSkill
- frontier-roundsSkill
- ghost-publishSkill
- hook-and-humanSkill
- interview-panelSkill
- job-feedsSkill
- markdown-converterSkill
- nano-banana-pro-jsonSkill
- python-drillSkill
- readabilitySkill
- report-builderSkill
- social-image-prepSkill
- source-snapshotSkill
- spec-readySkill
- terraform-registrySkill
- terragrunt-skillSkill
- transcribe-summarizeSkill
- travel-planningSkill
- trilium-captureSkill
- use-linearisSkill
- ux-auditSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Breakdown: Ask where the existing breakdown is (issue files, a tickets document, a beads list).
- Distinctive: line 34
If there is none, make one vertical slice per user story, then merge or split to size.
- Very specific: line 53
Check: Run check_tickets.py check <dir>/tickets.md and fix what you can.
- Very specific: line 62
Run check_tickets.py accept only when the person says so: check_tickets.py accept --tickets <dir>/tickets.md --rule <rule> [--slice <id or …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
spec-to-tickets
Breaking a spec into tickets is common; checking the result is not. Breakdowns come back as horizontal layers, with every ticket important, nothing held in reserve, and tickets nobody can trace to what the product is for. This skill is a thin layer over whatever breakdown exists: it rewrites it into one format, proposes priorities from the PRD, and has a script check it. Its centre is prioritising by outcome: what achieves the best result, and what to build now.
The rules above all others
- Prioritise by outcome. A Must is a Must because the PRD's goal, success check or anti-goal needs it, and the slice says which. Everything else is Should, Could or Won't Have this time.
- Vertical first. A slice cuts through every layer it needs and can be shown working on its own. Horizontal work is allowed only as a labelled prefactor or expand/migrate/contract step.
- No invented scope. A slice traces to a user story or a PRD line, or starts
Proposed:. - The person confirms; the script checks. You propose priorities and sizes; the person confirms
them in one round;
check_tickets.pychecks the result. - No personal data in the skill. DSDM is cited and paraphrased, never copied.
Steps
Scripts are in this skill's scripts/ directory; run them with uv run or python3.
- Inputs. Find the PRD and spec (spec-ready's
prd.mdandspec.md, or any others) and, when present,readiness.jsonbeside the PRD. - Breakdown. Ask where the existing breakdown is (issue files, a tickets document, a beads list). If there is none, make one vertical slice per user story, then merge or split to size.
- Rewrite it into
tickets.mdbeside the spec, in the format inreferences/tickets-format.md. Take the layers from the spec's implementation decisions, using its own names and its most specific split (each adapter it names, not "adapters"), and put the sentence that names them inlayers_from:. If the spec names none, or names them only as a proposal, writelayers_from: Proposed: <why>and ask once. The original breakdown stays untouched and is named insource:. - Propose and confirm, in one round. For every slice show its MoSCoW, size and trace, grouped
into increments of the timebox (one week unless the person names another), increment 1 a walking
skeleton. Before proposing, check the breakdown covers what the stories need to work at all (the
thing people act on has to be created somewhere), and that each half of the PRD's goal has a Must
early. Order increments by value, then fit the share: never put a Could in an earlier increment
than a Must it is the workaround for, or than a Must the PRD's goal names, just to keep an
increment under 60%. If ordering by value cannot keep it under, say so and ask. For every large Must, tell the person it could be broken down: name the parts, say which are
essential and which could wait, and why (a part with a workaround, such as swapping a shift by
dropping out and signing up again, can usually wait). The person confirms or changes the round;
you edit
tickets.md. A reply that does not answer what you asked ("go ahead") is not a confirmation: keep the open items open andProposed:, say which, and never write that the person agreed. When the person does agree to a proposal, itstracescites their turn,[turn:<id>]. - Check. Run
check_tickets.py check <dir>/tickets.mdand fix what you can. It exits 0 when clean, 1 on findings, and exits 2 when it is clean only because of attested overrides. It also lists every override it applied, everyProposed:slice, andsplit?advice on heavy Musts, so the person can see them. AProposed:slice counts toward neither the 60% share nor contingency until the person confirms it; do not add one to make the numbers work. A Must cannot beProposed:: it traces to the PRD's goal, success check or anti-goal. An acceptance criterion that needs a figure or a name the PRD and spec do not give (a length, a threshold, an app) startsProposed:too, and you show it in the confirm round. Before asking about an increment over 60% Must, split its heaviest Must into its parts and prioritise the parts, since often only part is a Must; if scope still cannot flex, offer an empty contingency increment at the end with the plan aimed at the date before it (references/rules.md). What only the person can decide (more than 60% Must in an increment, no Could, a Must with no trace), ask. Run check_tickets.py accept only when the person says so:check_tickets.py accept --tickets <dir>/tickets.md --rule <rule> [--slice <id or increment-N>] --turn <id> --quote "<their words>", where the turn is the one in which they decided and the quote is copied from it. Formixandcontingencythe slice is the increment, writtenincrement-N. If accept says "recorded as attested" (no transcript could be read), tell the person: their words were not checked. - Hand over. Name the slices whose blockers are done as ready. Each gets its plan from
superpowers:writing-plansjust in time, when work on it starts: a slice that depends on another is planned after that one is built. Create tickets only when the person asks, in what they use: beads (bd create, withbd dep addfor blockers), GitHub (gh issue create, blockers in the body), or Linear (theuse-linearisskill).
What the checks are
references/rules.md lists the checks and why each exists; references/worked-example.md
shows a breakdown that passes them; references/dsdm.md holds the DSDM points behind MoSCoW,
the 60% guidance and timeboxes.
Credit
The slicing ideas come from Matt Pocock's to-tickets (tracer-bullet vertical slices, blocking
edges, expand-migrate-contract) and Cole Medin's plan-create-stories and piv-slice-epic (slices
sized for one agent loop, parallel worktrees, just-in-time planning), both MIT; tracer bullets from
Andrew Hunt and David Thomas, The Pragmatic Programmer; MoSCoW, the Minimum Usable SubseT and
timeboxing from the DSDM Agile Project Framework, published by the DSDM Consortium.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

