A ticket-planning workflow that turns a broad goal into a sequence of small, shippable work items. It records dependencies and can reorder existing tickets or add a new one.

Use it to create, reorder, or append tickets in an open-ticket queue, with repository context and explicit dependencies.

It makes large goals easier to execute and verify by giving each ticket one focused acceptance check. It also prevents duplicate work and preserves the order needed for dependencies.

tickets — Skill for Claude Code by TweekFawkes/prompts

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 TweekFawkes/prompts --skill tickets

Clone the repo

git clone --depth 1 https://github.com/TweekFawkes/prompts

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/tweekfawkes/prompts/tickets/github.svg)](https://agentmods.dev/skills/tweekfawkes/prompts/tickets)

Your own site

<a href="https://agentmods.dev/skills/tweekfawkes/prompts/tickets"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/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/tweekfawkes/prompts/tickets"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 990 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.00031	$0.00990
Opus 5.5	$0.00012	$0.00396
Sonnet 5.5	$0.00006	$0.00198
Haiku 4.5	$0.00003	$0.00099

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

Security

Grade A, and why

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 1mo 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.

orcaflow/.claude/skills/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.

Tickets

Turn $ARGUMENTS into the smallest set of tickets that ship the goal, in the order a worker should run them. Three modes: a plain goal (default), --reorder, and --add <brief>.

1. Ground first

Read the newest file in z/handoffs/ (highest timestamp prefix) other than README.md; if none exist, say so and continue.
ls z/tickets/open z/tickets/closed.
date -u +%Y%m%d%H%M%S for the timestamp to stamp on new files.
For any repo lookup beyond these listings — does a symbol already exist, what does a file already do — dispatch the scout agent (Agent tool, subagent_type: scout) instead of reading files yourself. Keep the primary session small.

2. Plain goal: split and write

Break the goal into tickets small enough that one worker finishes one in under ~30 minutes, each with a single verifiable acceptance check. Prefer more, smaller tickets over one broad one.
Order by dependency: an earlier NNN must not need anything from a later NNN. Record real dependencies in each ticket's Depends on: field, not just filename order.
Dedup guard: before creating a file, check whether the goal already names an existing ticket (open or closed). If so, do not create a duplicate — say in your reply which ticket covers it.
Write each ticket with the template in z/tickets/README.md (read it there; do not duplicate it here). Filename: NNN-YYYYMMDDHHMMSS-slug.md. slug must be unique across open/ and closed/ ignoring the numeric and timestamp prefixes — grep both directories before picking.
Record every scope assumption inside the ticket itself (Context or Out of scope); never stop to ask the user.
Set Owner: per the README template: worker by default; a review, ship, or handoff ticket gets Owner: primary since the primary session runs those steps itself.
Set Priority: from --priority; without the flag write user. user is for goals the human stated. must and nice are for follow-ups a session discovered while working a ticket (/dowork always passes one of those two); never write user for such a follow-up.

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.

1mo ago First seen · 66 lines · 31 tokens per session scan A c29e718f4b47

Subscribe to this mod's changes

tickets is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 31 tokens to every session and 990 once invoked, about $0.0001 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-09-20.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens