Plan To Tickets

Community

AnastasiyaW

plan-to-tickets

Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be implemented directly, single-bug fixes, or chat-only summaries.

Overview

Publisher	AnastasiyaW
Repository	`codex-claude-code-config`
Skill name	`plan-to-tickets`
Stars	212
Forks	32
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by AnastasiyaW on GitHub. Read the source before you install it.

Installation

Install the Plan To Tickets AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git /tmp/codex-claude-code-config
mkdir -p .claude/skills
cp -r /tmp/codex-claude-code-config/skills/plan-to-tickets .claude/skills/plan-to-tickets

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Plan To Tickets in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Plan To Tickets on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Plan To Tickets is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

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

Frequently asked questions

What does the Plan To Tickets AI skill do?

Why use Plan To Tickets on TypingMind?

Because you install it once and use it with any model. Plan To Tickets is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Plan To Tickets in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Plan To Tickets?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Plan To Tickets?

As many as you like. As long as a model supports skills, you can use Plan To Tickets with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Plan To Tickets AI skill free?

Yes. It is published on GitHub by AnastasiyaW under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Plan To Tickets

Output Location

Required Ticket Shape

Slicing Rules

Workflow

Gotchas

Frequently asked questions

Related AI Skills

Set up your own AI workspace now