
to-tickets
Split a spec into self-contained tickets with dependencies.
- version
- 0.1.1
- GitHub stars
- 347
Install
/plugin install to-tickets@khanelinix-ai-toolsRun it inside Claude Code after adding the marketplace with /plugin marketplace add khaneliman/khanelinix.
Contents
Discovered from sourceSkills 1
To Tickets
Use only after the user explicitly invokes this skill. Decompose a saved spec, plan, or the current conversation into local, self-contained implementation tickets. This skill drafts tickets; it does not execute them.
Source and readiness
- Read the supplied spec or plan and relevant repository guidance. If the
source exists only in conversation, save a local spec snapshot first under
.planning/<feature>/spec.md; do not invoke$to-specautomatically. - Preserve a resolvable source path or link, source identity, and revision in
every ticket. Mark a ticket
readyonly when its prerequisites are verified complete and its material choices are settled; otherwise mark itblocked. Include anUnresolved choicesfield and never invent a decision to make a ticket appear ready. - Use an existing project convention or requested location when one exists.
Otherwise write tickets to
.planning/<feature>/tickets/NN-slug.md. Preserve unrelated snapshots and ticket files. On reruns, reuse matching tickets and IDs. Update task-owned drafts only when authorized; preserve unrelated and completed work. Allocate new IDs only for genuinely new slices. When the spec revision changes, flag affected tickets for revalidation before they are ready.
Decompose and write
- Create vertical, independently verifiable slices. Use an expand-contract sequence only when compatibility requires it.
- Give every ticket a unique stable ID and an acyclic dependency graph. Every dependency reference must resolve either to a ticket in this set or to an existing external prerequisite ticket with a resolvable path or link.
- No blocker does not make conflicting work safe to run simultaneously. Shared files, interfaces, contracts, migrations, or integration surfaces require serialized writes, or isolated worktrees followed by a named integration owner and explicit integration order. An integration ticket alone is not sufficient.
- Add an integration verification ticket when behavior crosses slice boundaries. Use ticket-template.md for every ticket and read each saved ticket back for completeness. Ensure every ticket fits one fresh session; split a slice that needs more context or work.
Each ticket must state its source spec revision, objective and non-goals,
acceptance criteria, constraints and interfaces, blocker ticket IDs, write scope
hints to verify at implementation time, exact verification commands or checks
with expected evidence, and a fresh-session instruction routing the work to
engineering-workflow or the project’s existing lifecycle owner.
Authority and publication
- Stop after drafting unless the next action is separately authorized. If execution, commits, publication, deployment, or activation are explicitly authorized, route execution to the existing project owner; this skill does not take over that lifecycle. Do not add a redundant approval gate for local drafts.
- Publish only when the user requests it. Use
github-toolkitfor GitHub, or an available tracker tool for another requested tracker. Preserve the local tickets and record publication identifiers after readback. Do not close or modify a parent issue as a side effect of ticket publication.
Sponsors
Details
- Marketplace
- khaneliman/khanelinix
- Source
- modules/common/ai-tools/skills/to-tickets
- Author
- khaneliman
- Category
- Developer Tools
More from khaneliman/khanelinix
All 43- typescript-best-practicesv0.1.6
- unslopv0.1.7
- verification-harnessv0.1.5
- whyv0.1.6
- ai-tools-architectv0.1.21
- architectv0.1.7
- arenav0.1.5
- bevy-toolkitv0.1.6
- blast-radiusv0.1.6
- blender-toolkitv0.3.2
- develop-web-gamev0.1.7
- diagnosing-bugsv0.1.3
- dotnet-toolkitv0.1.2
- engineering-principlesv0.1.22
- engineering-workflowv0.1.27
- figure-it-outv0.1.10
- git-toolkitv0.1.15
- github-toolkitv0.1.33
- howv0.1.7
- interrogatev0.1.10
- jj-toolkitv0.1.8
- lua-toolkitv0.2.0
- mcp-builderv0.1.6
- memory-profilerv0.1.6