Planning Tickets
Break requirements and design documents into GitHub Issues an implementing agent can ship without asking back: concrete values with their source, EARS requirements, explicit Not In Scope, machine-readable `Depends on #N` edges, a parallel-first breakdown, tracking parents with native sub-issues, and native blocked-by dependencies. Follows the repository's own issue conventions first — a triaging-issues skill's labels and body rules, a shipping-issues skill's ship contract — and falls back to its own templates only where the repository has none. Use when cutting tickets, breaking a feature or a
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill planning-ticketsgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/planning-tickets ~/.claude/skills/planning-ticketsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Planning Tickets An issue here is read by an agent that has none of this conversation: it must carry the real values, the boundary of the work, and its place in the order, or the agent guesses. The breakdown optimizes for parallel work — independent issues that do not touch the same files — and makes every ordering constraint explicit and machine-readable. ## 1. Read the repository's conventions Before drafting, look for the repository's own issue skills in its skills directory (`.claude/skills/` or `.agents/skills/` — check both) and forms (`.github/ISSUE_TEMPLATE/`, `.github/labels.yml`): - **`triaging-issues`** — its labels (type, `priority: P0`–`P3`, `blocked: …`, `tracking`), what a body must contain, and how an ordering constraint is spelled. These **replace** this skill's defaults wherever they differ: its label set instead of the fallback labels, its body requirements added to the skeleton, its dependency spelling exactly. - **`shipping-issues`** — the consumer. Read what it parses (its ship contract, e.g. a `` block, `touches=`, `design=`) and write every field it reads, so the backlog ranks and parallelizes without a research pass. - **Title style** — follow the repository's existing issues and forms. The bracket prefixes in [templates/issue-template.md](templates/issue-template.md) are only for repositories with no convention. ## 2. Plan the breakdown Sources are the documents, cited by path and section (`docs/product/requirements.md
Details
- Skill name
planning-tickets- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/planning-tickets/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Planning Tickets skill do?
Break requirements and design documents into GitHub Issues an implementing agent can ship without asking back: concrete values with their source, EARS requirements, explicit Not In Scope, machine-readable `Depends on #N` edges, a parallel-first breakdown, tracking parents with native sub-issues, and native blocked-by dependencies. Follows the repository's own issue conventions first — a triaging-issues skill's labels and body rules, a shipping-issues skill's ship contract — and falls back to its own templates only where the repository has none. Use when cutting tickets, breaking a feature or a
How do I install the Planning Tickets skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Planning Tickets popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Ship It
5Magnus-Gille/claude-skills
Use for an explicit /ship-it request or an end-to-end request to deliver a scoped repository task to its selected local, PR, merge, or verified-production endpoint; not for isolated local edits, review-only, or deploy-only tasks.
M5 Delegate
5Magnus-Gille/claude-skills
Delegate a self-contained task to Magnus's M5 when local inference is requested or the project's delegation policy applies.
Airtable
9Lord1Egypt/RA-Skills
Airtable REST API via curl. Records CRUD, filters, upserts.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.