A planning workflow that breaks a large goal into small, complete work slices, with a local map and one document for each slice. A work slice covers the connected changes needed to demonstrate one narrow result.

Use it to turn a plan or conversation into local tickets, identify preparation work, and optionally mirror the tickets to GitHub when requested.

It makes large changes easier to implement and verify one piece at a time without losing the overall plan.

to-tickets — Skill for Claude Code by asteasolutions/ai-toolkit

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add asteasolutions/ai-toolkit --skill to-tickets

Clone the repo

git clone --depth 1 https://github.com/asteasolutions/ai-toolkit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/to-tickets/github.svg)](https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-tickets)

Your own site

<a href="https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-tickets"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/to-tickets/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-tickets"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/to-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 726 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00059	$0.00726
Opus 5.5	$0.00024	$0.00290
Sonnet 5.5	$0.00012	$0.00145
Haiku 4.5	$0.00006	$0.00073

Measured 2mo ago against content hash 733997bb4f30, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

to-tickets scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/setup/templates/to-tickets/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

to-tickets

Decompose work into tracer-bullet vertical slices. Write helm's work-tree shapes: _map.md plus one leaf doc per ticket (see helm/references/artifacts.md if present).

Publish policy

Always write local under .scratch/<goal-slug>/ — this is the program counter.
Also mirror to GitHub only when the user asks for GitHub, or already pointed at an issue URL/id. If docs/agents/issue-tracker.md exists, follow its GitHub conventions for that mirror.
Never skip the local write. Never ask which tracker after a local-only run.

Process

1. Gather context

Work from the conversation. If the user passes a reference (spec path, issue number/URL), fetch and read it.

2. Explore (optional)

If needed, explore the codebase. Prefer any domain vocabulary the repo already has. Look for prefactoring — make the change easy, then make the easy change. Prefactoring is its own ticket, done first.

3. Draft vertical slices

Each ticket:

Cuts a narrow but complete path through every layer it touches (schema, logic, interface, tests) — vertical, not horizontal
Is demoable / verifiable on its own
Fits in one fresh context as one change

Give each ticket blocking edges — tickets that must finish before it starts.

Wide refactors (one mechanical change with huge blast radius) are the exception: sequence as expand → migrate batches → contract, not forced tracer bullets.

4. Quiz the developer

Present a numbered list: Title · Blocked by · What it delivers. Ask granularity, edges, merge/split. Iterate until approved.

5. Write local artifacts

_map.md — overarching intent + ordered task list with status and blockers:

# <goal title>

## Intent
<overarching what + why>

## Tasks
1. [pending] <task-slug>
2. [pending] <task-slug> — blocked by: 1

One leaf doc per ticket at .scratch/<goal-slug>/<task-slug>.md — Intent only at creation (Plan comes later when that leaf is planned):

Read the full file on GitHub · 77 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

LICENSE 1.1 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 77 lines · 59 tokens per session scan A 733997bb4f30

Subscribe to this mod's changes

to-tickets is a skill published in the GitHub repository asteasolutions/ai-toolkit (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 726 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning

to-tickets next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
to-ticketsasteasolutions/ai-toolkit	Skill	5	1mo ago	MIT	A	59	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex

to-tickets

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

to-tickets

Publish policy

Process

1. Gather context

2. Explore (optional)

3. Draft vertical slices

4. Quiz the developer

5. Write local artifacts

What ships with it

What this file has done since we first saw it

to-tickets compared with skills from other repositories