What is plan-to-tickets?

A ticket-writing workflow that turns a large plan, product requirements document, feature, refactor, or research plan into small coding tasks. Each task includes what to build, how to check it, and what blocks it.

Use it to create local Markdown tickets for multi-step engineering work, with acceptance checklists, verification commands, and narrow end-to-end slices through the system.

It removes the work of breaking a broad request into tasks that an agent can complete and verify independently. It also makes missing acceptance criteria and dependencies visible before implementation starts.

plan-to-tickets — Skill for Claude Code by AnastasiyaW

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 AnastasiyaW/codex-claude-code-config --skill plan-to-tickets

Clone the repo

git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config

Made for: Claude Code.

Or install harness, the plugin that ships this one along with the rest of its 59 skills, 8 agents, 4 hooks.

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/anastasiyaw/codex-claude-code-config/plan-to-tickets/github.svg)](https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/plan-to-tickets)

Your own site

<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/plan-to-tickets"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/plan-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/anastasiyaw/codex-claude-code-config/plan-to-tickets"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/plan-to-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 591 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00074	$0.00591
Opus 5.5	$0.00030	$0.00236
Sonnet 5.5	$0.00015	$0.00118
Haiku 4.5	$0.00007	$0.00059

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

Security

Grade A, and why

plan-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.

skills/plan-to-tickets/SKILL.md · 66 lines

How it starts

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

Plan To Tickets

Turn a large plan into small, independently executable tickets. Use this before handing a broad plan to agents, before long autonomous work, or when the user asks for tickets/issues/slices.

Output Location

If no issue tracker is explicitly selected, write local tickets under:

<project>/.agent/tickets/<YYYY-MM-DD>-<slug>/

Each ticket is one Markdown file:

TICKET-001-short-slug.md

Required Ticket Shape

Each ticket must include these headings exactly:

## Status
## Parent
## What To Build
## Acceptance Criteria
## Verification
## Blocked By
## Notes

## Status must contain ready-for-agent only when all acceptance criteria and verification steps are concrete.

## Acceptance Criteria must contain checklist items (- [ ] ...).

## Verification must contain at least one command, script, test, artifact check, or explicit manual-review gate.

Slicing Rules

Prefer vertical tracer bullets: a narrow complete path through the required layers, not "all backend" then "all UI" then "all tests".
A ticket must be independently verifiable.
Put prefactoring first only when it makes a later slice smaller or safer.
Keep dependencies explicit in ## Blocked By; write None when it can start immediately.
Do not include stale-prone file paths unless the path is already a stable contract or current codebase evidence.
Do not publish external tracker issues unless the user asked for that tracker.

Workflow

Read the plan/spec and current repo context needed to avoid fake tickets.
Draft ticket files in dependency order.
Run the validator:

python "$env:USERPROFILE\.claude\claude-code-config\scripts\validate_agent_tickets.py" --tickets-dir <ticket-dir>

Fix every validator failure before claiming the ticket split is ready.
Report the ticket directory and the count of ready tickets.

Gotchas

Horizontal tickets overload later agents. If a ticket cannot be verified alone, split it differently.
"Implement feature" is not an acceptance criterion. ACs must describe observable behavior or artifacts.
"Run tests" alone is weak verification. Name the test command or the artifact that proves success.
Do not use this to postpone work. Ticketization is for large plans; small tasks should be implemented directly.

Read the full file on GitHub · 66 lines

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 · 66 lines · 74 tokens per session scan A a463758ffb33

Subscribe to this mod's changes

plan-to-tickets is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (212 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 591 once invoked, about $0.0003 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-30.

Claude Code LLM Project management ai-agents claude machine-learning prompt-engineering

zero-to-prod-orchestrator

Master orchestrator to build an application from scratch to a production-ready release, enforcing strict step-by-step progression and continuous documentation / Orkestrator utama untuk membangun aplikasi dari nol hingga rilis siap produksi dengan dokumentasi bertahap.

roedyrustam/vibes-plug · 55 tokens

plan-to-tickets