User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Split an agreed plan or spec into actionable tickets with acceptance criteria and blocking dependencies.
Install To Tickets
$ npx skills add nodetool-ai/nodetool --skill to-tickets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool 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/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/to-tickets .claude/skills/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 "to-tickets" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/.agents/skills/to-tickets into .claude/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/nodetool-ai/nodetool/tree/main/.agents/skills/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 nodetool-ai/nodetool --skill to-tickets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool to-tickets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/to-tickets .agents/skills/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 "to-tickets" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/.agents/skills/to-tickets into .agents/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 nodetool-ai/nodetool --skill to-tickets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool to-tickets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/to-tickets .cursor/skills/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 "to-tickets" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/.agents/skills/to-tickets into .cursor/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/nodetool-ai/nodetool.git --path .agents/skills/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 nodetool-ai/nodetool --skill to-tickets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool to-tickets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/to-tickets .gemini/skills/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 "to-tickets" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/.agents/skills/to-tickets into .gemini/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 nodetool-ai/nodetool 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 nodetool-ai/nodetool --skill to-tickets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/to-tickets .github/skills/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 "to-tickets" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/.agents/skills/to-tickets into .github/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 nodetool-ai/nodetool --skill 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 nodetool-ai/nodetool to-tickets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/to-tickets .opencode/skills/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 "to-tickets" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/.agents/skills/to-tickets into .opencode/skills/to-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
to-tickets- GitHub stars
- 560
- Token cost
- ~1.5k tokens
- SKILL.md length
- 846 words
- Files
- 2
- Skills in repo
- 127
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Split an agreed plan or spec into actionable tickets with acceptance criteria and blocking dependencies.
- Works in 5 steps: Gather context → Explore the codebase (optional) → Draft vertical slices → …
- Tasks that involve User stories
- SKILL.md covers Process, Parent, What to build and Acceptance criteria, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
To Tickets is an agent skill from nodetool-ai/nodetool. Split an agreed plan or spec into actionable tickets with acceptance criteria and blocking dependencies. Draft or publish as requested.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Product & Project Management, covering User stories. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve User stories
Example prompts
- “/to-tickets”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 339f069. 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
No scripts in the folder and no shell commands in SKILL.md.
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
To Tickets loads about 1.5k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 846 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 nodetool-ai/nodetool at commit 339f069, republished under its AGPL-3.0 licence (© nodetool-ai). 846 words, ~1,464 tokens.
Download SKILL.mdSave it as
.claude/skills/to-tickets/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- to-tickets
- description
- Split an agreed plan or spec into actionable tickets with acceptance criteria and blocking dependencies. Draft or publish as requested.
- disable-model-invocation
- true
To Tickets
Break a plan, spec, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring the tickets that block it.
Use the configured tracker and existing labels. If the publication destination is missing, prepare the tickets locally before asking where to publish. Do not run repository setup as a prerequisite to drafting.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
Include preparatory refactoring only when it is necessary to deliver the requested behavior.
3. Draft vertical slices
Break the work into tracer bullet tickets.
<vertical-slice-rules>- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer
- A completed slice is demoable or verifiable on its own
- Each slice is sized to fit in a single fresh context window
- Sequence necessary preparation before the slices that depend on it
</vertical-slice-rules>Give each ticket its blocking edges — the other tickets that must complete before it can start. A ticket with no blockers can start immediately.
Wide refactors are the exception to vertical slicing. A wide refactor is one mechanical change — rename a column, retype a shared symbol — whose blast radius fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as expand–contract. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.
4. Check the breakdown
Check that every acceptance criterion belongs to a ticket and that blocking edges reflect actual dependencies without cycles. Summarize titles, dependencies, and what each ticket delivers.
Use the agreed scope and granularity. If the user asked to create the tickets, continue to publication without a routine approval round. Ask only about an unresolved choice that materially changes the scope or dependencies. If the user asked to review a draft first, deliver the complete draft and wait for that review.
Show full SKILL.md (366 more words)Show less
5. Publish the tickets to the configured tracker
Publish when authorized by the request or session context. How depends on the configured tracker — the tickets are the same either way, only the shape of the blocking edges changes:
- Local files → write one file per ticket under
.scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from01in dependency order (blockers first). Each file's "Blocked by" lists the numbers/titles it depends on. Use the per-ticket file template below — one ticket per file, never a single combined file. - A real issue tracker (GitHub, Linear, …) → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking / sub-issue relationship where it has one; otherwise set each ticket's "Blocked by" to the blocking issues. Apply the
ready-for-agenttriage label unless instructed otherwise — the tickets are agent-grabbable by construction.
Work the frontier: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.
Keep parent issue changes outside this task unless the user requested them. Read back created tickets and dependency links, then return their URLs or paths. After a partial failure, check which tickets exist before retrying to avoid duplicates.
<local-ticket-template><NN> — <Ticket title>
What to build: the end-to-end behaviour this ticket makes work, from the user's perspective — not a layer-by-layer implementation list.
Blocked by: the numbers/titles of the tickets that gate this one, or "None — can start immediately".
Status: ready-for-agent
- Acceptance criterion 1
- Acceptance criterion 2
</local-ticket-template><issue-template>Parent
A reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).
What to build
The end-to-end behaviour this ticket makes work, from the user's perspective — not layer-by-layer implementation.
Acceptance criteria
- Criterion 1
- Criterion 2
Blocked by
- A reference to each blocking ticket, or "None — can start immediately".
</issue-template>Include stable source paths when they make a ticket actionable. Prefer links over copied implementation. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/to-tickets of nodetool-ai/nodetool.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 339f069
Compare with similar skills
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 |
|---|---|---|---|---|---|---|
| To Tickets this skillnodetool-ai/nodetool | 560 | — | ~1.5k | Automated safety check: Pass | AGPL-3.0 | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from nodetool-ai/nodetool
All 127 skills in this repoBeat Sync Editing
nodetool-ai/nodetool
Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.
Caption Titles
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
Color Motion
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
Commercial Beat Sheet
nodetool-ai/nodetool
Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.
Elevenlabs Audio Prompting
nodetool-ai/nodetool
Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…
Frame Composition
nodetool-ai/nodetool
Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.
Related
Categories
Questions about To Tickets
What does To Tickets do?
Split an agreed plan or spec into actionable tickets with acceptance criteria and blocking dependencies. To Tickets is an agent skill from nodetool-ai/nodetool. Split an agreed plan or spec into actionable tickets with acceptance criteria and blocking dependencies.
When should I use To Tickets?
To Tickets fits situations like: tasks that involve User stories.
How do I install To Tickets in Claude Code?
Run `npx skills add nodetool-ai/nodetool --skill to-tickets -a claude-code`. Or copy the skill folder (.agents/skills/to-tickets in nodetool-ai/nodetool) into .claude/skills/to-tickets in your project. Claude Code loads it when a task matches its description.
How do I install To Tickets in Codex?
Run `npx skills add nodetool-ai/nodetool --skill to-tickets -a codex`. Or copy the skill folder (.agents/skills/to-tickets in nodetool-ai/nodetool) into .agents/skills/to-tickets in your project. Codex loads it when a task matches its description.
Can I use 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 nodetool-ai/nodetool --skill 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/to-tickets, .gemini/skills/to-tickets, .github/skills/to-tickets and .opencode/skills/to-tickets in your project.
What does To Tickets need to run?
SKILL.md names no scripts, command-line tools or credentials: To Tickets is instructions for the agent only.
Does 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 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 To Tickets use?
To Tickets is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does To Tickets use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 To Tickets?
Skills that share tags, products or a category with To Tickets: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains To Tickets?
nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 10, 2026.
Source: nodetool-ai/nodetool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.