Grilling Ideas
opsmill/infrahub
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written.
A skill your agent uses 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…
Install Plan To Tickets
$ npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config plan-to-tickets --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan-to-tickets .claude/skills/plan-to-tickets && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-to-tickets" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets into .claude/skills/plan-to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-to-tickets", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-ticketsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config plan-to-tickets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan-to-tickets .agents/skills/plan-to-tickets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-to-tickets" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets into .agents/skills/plan-to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-to-tickets", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config plan-to-tickets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan-to-tickets .cursor/skills/plan-to-tickets && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-to-tickets" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets into .cursor/skills/plan-to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-to-tickets", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AnastasiyaW/codex-claude-code-config.git --path skills/plan-to-tickets--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config plan-to-tickets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan-to-tickets .gemini/skills/plan-to-tickets && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-to-tickets" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets into .gemini/skills/plan-to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-to-tickets", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AnastasiyaW/codex-claude-code-config plan-to-ticketsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan-to-tickets .github/skills/plan-to-tickets && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-to-tickets" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets into .github/skills/plan-to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-to-tickets", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config plan-to-tickets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan-to-tickets .opencode/skills/plan-to-tickets && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-to-tickets" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/plan-to-tickets into .opencode/skills/plan-to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-to-tickets", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-to-tickets- GitHub stars
- 154
- Token cost
- ~683 tokens
- SKILL.md length
- 307 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Works in 5 steps: Read the plan/spec and current repo… → Draft ticket files in dependency order. → Run the validator → …
- Multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria
- SKILL.md covers Output Location, Required Ticket Shape, Slicing Rules and Workflow, plus 1 more section
- Calls python
What it does
Plan To Tickets is an agent skill from AnastasiyaW/codex-claude-code-config. 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.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories, Debugging and PRD writing. The repository describes itself as: Claude Code, Codex, and multi-agent configuration system: principles, hooks, skills, and workflow patterns for AI-assisted development. The licence is MIT.
When your agent uses it
- Multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria
- Verification commands
- Vertical tracer-bullet slices
- Small tasks that should be implemented directly
Example prompts
- “/plan-to-tickets”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the plan/spec and current repo context needed to avoid fake tickets.
- Draft ticket files in dependency order.
- Run the validator
- Fix every validator failure before claiming the ticket split is ready.
- Report the ticket directory and the count of ready tickets.
What it can do on your machine
Read from SKILL.md and the folder at commit 67709af. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plan To Tickets loads about 683 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 307 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AnastasiyaW/codex-claude-code-config at commit 67709af, republished under its MIT licence (© AnastasiyaW). 307 words, ~683 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-to-tickets/SKILL.md (or your agent's skills folder).- name
- plan-to-tickets
- description
- 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.
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; writeNonewhen 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.
© AnastasiyaW, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/plan-to-tickets of AnastasiyaW/codex-claude-code-config.
Open the folder on GitHubat commit 67709af
Compare with similar skills
Plan To Tickets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan To Tickets this skillAnastasiyaW/codex-claude-code-config | 154 | — | ~683 | Automated safety check: Pass | MIT | |
| Grilling Ideasopsmill/infrahub | 534 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Spec Workflowhashgraph-online/awesome-codex-plugins | 1.3k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Counterexample ExplainerArabelaTso/Skills-4-SE | 253 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Analyze And Planadobe/skills | 197 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Spec Workflow
hashgraph-online/awesome-codex-plugins
This skill should be used when the user asks to "create a spec", "write requirements", "design a feature", "plan implementation", "use EARS notation", "create user stories", "break down tasks"…
Counterexample Explainer
ArabelaTso/Skills-4-SE
Explain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories…
Analyze And Plan
adobe/skills
Use this when you need to define acceptance criteria, write requirements, scope work, or create a definition of done for AEM Edge Delivery Services (EDS) tasks such as new blocks, variants, behavior…
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
More from AnastasiyaW/codex-claude-code-config
All 50 skills in this repoBug Reproducer
AnastasiyaW/codex-claude-code-config
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.
Motion Framer
AnastasiyaW/codex-claude-code-config
A skill your agent uses when implementing Motion or Framer Motion in React/JavaScript: interactive UI components, micro-interactions, gestures, layout or page transitions, and scroll-based animation.
Proof Verify
AnastasiyaW/codex-claude-code-config
Plan-based verification - freeze acceptance criteria before building, then verify after with an independent fresh-context agent (the builder must not verify their own work).
Workflow Orchestration
AnastasiyaW/codex-claude-code-config
Написание и запуск Claude Code dynamic workflows (JS-оркестратор субагентов).
Notebooklm Grounded Research
AnastasiyaW/codex-claude-code-config
A skill your agent uses when: NotebookLM, notebooklm MCP, large documentation sets, courses, books, papers, or citation-backed research are mentioned.
Deepseek Provider Contract
AnastasiyaW/codex-claude-code-config
Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries.
Related
Categories
Questions about Plan To Tickets
What does Plan To Tickets do?
A skill your agent uses 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…. Plan To Tickets is an agent skill from AnastasiyaW/codex-claude-code-config. 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.
When should I use Plan To Tickets?
Plan To Tickets fits situations like: multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria; verification commands; vertical tracer-bullet slices; small tasks that should be implemented directly.
How do I install Plan To Tickets in Claude Code?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a claude-code`. Or copy the skill folder (skills/plan-to-tickets in AnastasiyaW/codex-claude-code-config) into .claude/skills/plan-to-tickets in your project. Claude Code loads it when a task matches its description.
How do I install Plan To Tickets in Codex?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a codex`. Or copy the skill folder (skills/plan-to-tickets in AnastasiyaW/codex-claude-code-config) into .agents/skills/plan-to-tickets in your project. Codex loads it when a task matches its description.
Can I use Plan To Tickets in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AnastasiyaW/codex-claude-code-config --skill plan-to-tickets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-to-tickets, .gemini/skills/plan-to-tickets, .github/skills/plan-to-tickets and .opencode/skills/plan-to-tickets in your project.
What does Plan To Tickets need to run?
Going by SKILL.md and its folder, Plan To Tickets needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Plan To Tickets access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Plan To Tickets safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plan To Tickets use?
Plan To Tickets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan To Tickets use?
About 683 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Plan To Tickets?
Skills that share tags, products or a category with Plan To Tickets: Grilling Ideas (opsmill/infrahub, 534 stars), Spec Workflow (hashgraph-online/awesome-codex-plugins, 1.3k stars), Counterexample Explainer (ArabelaTso/Skills-4-SE, 253 stars) and Analyze And Plan (adobe/skills, 197 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan To Tickets?
AnastasiyaW (a GitHub user) maintains it in AnastasiyaW/codex-claude-code-config, which has 154 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.
Source: AnastasiyaW/codex-claude-code-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.