New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Roadmap Tickets

by ruby-git in ruby-git/ruby-git

Publishes a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and milestones, keeping existing issues reconciled.

MITAuto-check passedProduct & Project Management

Install Roadmap Tickets

skills CLI
$ npx skills add ruby-git/ruby-git --skill roadmap-tickets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruby-git/ruby-git roadmap-tickets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/roadmap-tickets .claude/skills/roadmap-tickets && rm -rf skills-src

Use ~/.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/

Facts

Skill name
roadmap-tickets
GitHub stars
1.8k
Token cost
~1.5k tokens
SKILL.md length
652 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Publishes a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and milestones, keeping existing issues reconciled.

  • Works in 6 steps: Gather the plan from the conversation or… → Reconcile first: list existing issues in… → Draft the tickets with the template… → …
  • Conversation into tracker tickets
  • SKILL.md covers Contents, How to use this skill, Related skills and Where the mechanics live, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Roadmap Tickets is an agent skill from ruby-git/ruby-git. Publishes a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and milestones, keeping existing issues reconciled. Use when turning a plan or conversation into tracker tickets, building or extending a release roadmap, adding blocking edges or an umbrella issue, or querying the frontier of workable issues.

Its SKILL.md is about 1.5k 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 Project management. It works with GitHub. The repository describes itself as: Ruby/Git is a Ruby library that can be used to create, read and manipulate Git repositories by wrapping system calls to the git binary. The licence is MIT.

When your agent uses it

  • Conversation into tracker tickets
  • Extending a release roadmap
  • Adding blocking edges
  • An umbrella issue

Example prompts

  • “Use the roadmap-tickets skill to publish a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and…”
  • “/roadmap-tickets”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Gather the plan from the conversation or the referenced document/issue,
  2. Reconcile first: list existing issues in the area; decide per item
  3. Draft the tickets with the template below, each with its blocking edges.
  4. Quiz the maintainer: present the breakdown (title, blocked-by, what it
  5. Publish in dependency order; then wire sub-issues, edges, and milestones
  6. Verify: the frontier query returns exactly the tickets that should be

What it can do on your machine

Read from SKILL.md and the folder at commit f3bf20f. 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 (its code samples are markdown).

    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

Roadmap Tickets loads about 1.5k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 652 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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 ruby-git/ruby-git at commit f3bf20f, republished under its MIT licence (© ruby-git). 652 words, ~1,480 tokens.

Download SKILL.mdSave it as .claude/skills/roadmap-tickets/SKILL.md (or your agent's skills folder).
name
roadmap-tickets
description
Publishes a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and milestones, keeping existing issues reconciled. Use when turning a plan or conversation into tracker tickets, building or extending a release roadmap, adding blocking edges or an umbrella issue, or querying the frontier of workable issues.

Roadmap Tickets

Publish a plan as tracker tickets and keep the roadmap structure — umbrella, edges, milestones, and the issue bodies the plan touches — consistent on the tracker. Ported from the mattpocock to-tickets convention after the v6.0.0 roadmap trial (issue 1717); this file is the repository's own record of how plans become tickets here.

Contents

How to use this skill

Attach this file to your context and invoke it with the plan, spec, or conversation to publish. The tracker work is done with the gh CLI; the maintainer approves the breakdown before anything is published.

Where the mechanics live

The gh command conventions and the native-relationship API calls (sub-issues, blocked-by edges with database ids, the frontier query) are recorded once, in docs/agents/issue-tracker.md — "Wayfinding operations", which is the authority. This skill states the process; consult that file for the exact commands rather than reconstructing them.

Conventions

Tickets
  • A ticket is a vertical slice: complete and verifiable on its own, sized to fit one fresh agent session. Each declares its blocking edges; a ticket with no blockers is immediately workable.
  • Blocking edges are GitHub's native issue dependencies. The ticket body's "Blocked by" section documents the same edges for readers, but only the native edge gates — prose alone cannot render the frontier. A ticket is unblocked when every blocker is closed; is:open -is:blocked in the issues search renders the workable set.
  • Publish in dependency order (blockers first) so every "Blocked by" section references real issue numbers.
  • Apply no triage labels — this repository has not adopted a triage label vocabulary.
  • The maintainer reviews every ticket before it posts; per AI_POLICY.md, no AI-disclosure line is added.
Umbrella issues
  • An umbrella is an index, not a store: it gists each decision in one or two lines and links to the sub-issue that holds the detail. Detail lives in exactly one place.
  • Every roadmap item is a sub-issue of the umbrella (GitHub renders the progress bar from this). A release umbrella stays gates-only: work that does not gate the release is linked from prose, not added as a sub-issue.
  • Record decisions with their date. Durable decisions with a rejected alternative go to docs/adr/ per its README; the umbrella links the ADR rather than restating it.
Show full SKILL.md (232 more words)Show less
Reconciliation
  • Before drafting, list the open issues in the plan's area: reference existing issues instead of recreating them, and give them milestones and edges rather than duplicate tickets.
  • When the plan contradicts an existing issue body (a timeline, a scope, a version number), update that body in the same publication — a dated note at the top stating the re-mapping — so no issue contradicts the roadmap. Stale bodies that outlive their plans are the failure mode this whole convention exists to prevent.
  • Milestone assignments are part of publication, not an afterthought; create or retire milestones as the roadmap requires.

Workflow

  1. Gather the plan from the conversation or the referenced document/issue, and read the ADRs covering the area.
  2. Reconcile first: list existing issues in the area; decide per item whether it is referenced, re-milestoned, body-updated, or genuinely new.
  3. Draft the tickets with the template below, each with its blocking edges.
  4. Quiz the maintainer: present the breakdown (title, blocked-by, what it delivers per ticket) and iterate until approved. Nothing posts before approval.
  5. Publish in dependency order; then wire sub-issues, edges, and milestones per the issue-tracker doc.
  6. Verify: the frontier query returns exactly the tickets that should be workable, and nothing meant to be gated appears in it. The publication is complete when the verification matches the approved breakdown and every contradicted issue body has its re-map note.

Ticket template

markdown
## Parent

Part of <the umbrella/roadmap issue>. (Omit when there is no parent.)

## What to build

The end-to-end behavior this ticket makes work, from the caller's perspective —
not a layer-by-layer implementation list. Name classes and methods, not file
paths, which go stale.

## Acceptance criteria

- [ ] Checkable criterion
- [ ] ...

## Blocked by

- The blocking issues — each is also wired as a native blocked-by edge at
  publication — or "None — can start immediately".

© ruby-git, 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 .github/skills/roadmap-tickets of ruby-git/ruby-git.

Open the folder on GitHubat commit f3bf20f

Compare with similar skills

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

Roadmap Tickets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Roadmap Tickets this skillruby-git/ruby-git1.8k—~1.5kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Project Managerpwrdrvr/openclaw-codex-app-server265—~1.5kAutomated safety check: PassMIT
Find Project Anomaliespenpot/penpot61k—~1.2kAutomated safety check: PassMPL-2.0
PublishQ00/ouroboros6.2k—~2.7kAutomated safety check: PassMIT
Gh Read Inspectoreclipse-rdf4j/rdf4j420—~950Automated safety check: PassBSD-3-Clause

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Project Manager

    pwrdrvr/openclaw-codex-app-server

    Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync.

    265 GitHub stars~1.5k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Find Project Anomalies

    penpot/penpot

    Check a GitHub milestone against the Main project board, report the five anomaly types to tmp/<MILESTONE-ANOMALIES.md, and fix missing milestone assignments on request.

    61k GitHub stars~1.2k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Publish

    Q00/ouroboros

    Publish Seed specification as GitHub Issues for team-based project management

    6.2k GitHub stars~2.7k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Gh Read Inspector

    eclipse-rdf4j/rdf4j

    Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.

    420 GitHub stars~950 tokensUpdated today
    Product & Project ManagementAuto-check passed

  • GitHub Project Management Swarm

    ruvnet/agentic-flow

    Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.

    816 GitHub starsUsed in 6 repos~7.1k tokens
    Product & Project ManagementAuto-check passed

More from ruby-git/ruby-git

All 30 skills in this repo

  • Address PR Feedback for ruby-git

    ruby-git/ruby-git

    Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…

    1.8k GitHub stars~657 tokensUpdated 6 days ago
    Auto-check passed

  • Breaking Change Analysis

    ruby-git/ruby-git

    Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.

    1.8k GitHub stars~1.7k tokensUpdated 6 days ago
    Auto-check passed

  • CI/CD Failure Troubleshooting

    ruby-git/ruby-git

    Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 6 days ago
    Auto-check passed

  • Git Command Class Implementation

    ruby-git/ruby-git

    Scaffolds and reviews `Git::Commands::*` classes in the ruby-git library, with unit tests, integration tests and YARD docs, using the Base command architecture.

    1.8k GitHub stars~3k tokensUpdated 6 days ago
    Auto-check passed

  • Gem Dependency Management

    ruby-git/ruby-git

    Workflow for updating gem dependencies and fixing CVEs in the ruby-git project: assess with bundle outdated and audit, edit the gemspec, test, then commit with conventional messages.

    1.8k GitHub stars~806 tokensUpdated 6 days ago
    Auto-check passed

  • Extract Command from Git::Lib

    ruby-git/ruby-git

    Migrates a direct command call in Ruby Git's Git::Lib to a Git::Commands class, as part of a Strangler Fig redesign, with a plan, legacy tests and a pull request.

    1.8k GitHub stars~4.4k tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Roadmap Tickets

What does Roadmap Tickets do?

Publishes a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and milestones, keeping existing issues reconciled. Roadmap Tickets is an agent skill from ruby-git/ruby-git. Publishes a plan, spec, or decision set as GitHub issues with native blocking edges, sub-issue umbrellas, and milestones, keeping existing issues reconciled.

When should I use Roadmap Tickets?

Roadmap Tickets fits situations like: conversation into tracker tickets; extending a release roadmap; adding blocking edges; an umbrella issue.

How do I install Roadmap Tickets in Claude Code?

Run `npx skills add ruby-git/ruby-git --skill roadmap-tickets -a claude-code`. Or copy the skill folder (.github/skills/roadmap-tickets in ruby-git/ruby-git) into .claude/skills/roadmap-tickets in your project. Claude Code loads it when a task matches its description.

How do I install Roadmap Tickets in Codex?

Run `npx skills add ruby-git/ruby-git --skill roadmap-tickets -a codex`. Or copy the skill folder (.github/skills/roadmap-tickets in ruby-git/ruby-git) into .agents/skills/roadmap-tickets in your project. Codex loads it when a task matches its description.

Can I use Roadmap 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 ruby-git/ruby-git --skill roadmap-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/roadmap-tickets, .gemini/skills/roadmap-tickets, .github/skills/roadmap-tickets and .opencode/skills/roadmap-tickets in your project.

What does Roadmap Tickets need to run?

SKILL.md names no scripts, command-line tools or credentials: Roadmap Tickets is instructions for the agent only.

Does Roadmap 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 Roadmap 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 Roadmap Tickets use?

Roadmap 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 Roadmap 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 Roadmap Tickets?

Skills that share tags, products or a category with Roadmap Tickets: CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Manager (pwrdrvr/openclaw-codex-app-server, 265 stars), Find Project Anomalies (penpot/penpot, 61k stars) and Publish (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Roadmap Tickets?

ruby-git (a GitHub organization) maintains it in ruby-git/ruby-git, which has 1,799 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 2, 2026.

Source: ruby-git/ruby-git on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.