roadmap

Manages epic entries across four horizons in a GitHub-backed ROADMAP.md file.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/chris-prener/dev-kit --skill roadmap-chris-prener
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roadmap
Source: https://github.com/chris-prener/dev-kit/tree/main/dev-kit/skills/roadmap
Command: npx skills add https://github.com/chris-prener/dev-kit --skill roadmap-chris-prener

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a project roadmap document in sync with the actual state of GitHub epic issues is tedious and error-prone. This Skill owns the Epics section of docs/ROADMAP.md, adding, moving, and pruning epic entries while validating every entry against the live GitHub issue as the source of truth. ## Core Features & Use Cases - Add and move epics across horizons: Register newly filed epics into Now, Next, Later, or Recently Shipped, with title and milestone derived live from the GitHub issue via the gh CLI. - Structural validation and reformatting: On every invocation, validate all entries against a canonical format, flag DRIFT and STALE entries, and repair them only on explicit reformat trigger. - Automatic pruning: Keep Recently Shipped capped at the 10 newest closed epics, with older ones remaining discoverable via GitHub labels. - Use Case: After closing an epic issue, invoke the skill to move the entry into Recently Shipped, re-derive its milestone from the issue, and prune the section back to 10 entries in one operation. ## Quick Start Ask Claude to add epic issue 42 to the Later horizon of the roadmap, or to validate the Epics section of docs/ROADMAP.md.

Frequently Asked Questions about roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a GitHub epic issue to a roadmap document?▼

Invoke the skill with the add operation and the epic issue number, optionally specifying a target horizon. It verifies the issue is open and labeled epic, derives the title and milestone via gh issue view, and inserts a canonical entry, defaulting to the Later horizon.

How do I move an epic between roadmap horizons in Markdown?▼

Use the move operation with the issue number and target horizon. The skill locates the existing entry by issue URL, re-derives title and milestone from the live issue, checks state consistency, and reinserts it following the horizon ordering rules.

Does the roadmap skill work with GitHub issues?▼

Yes, it treats the GitHub issue as the source of truth for every entry. It uses gh issue view to resolve titles, states, labels, and milestones, and requires the epic label on any issue it operates on.

What happens when the Recently Shipped section exceeds 10 entries?▼

The skill prunes the oldest entries from the bottom of the list until exactly 10 remain, either automatically after a move into Recently Shipped or via an explicit prune operation. Pruned epics stay discoverable through the is:closed label:epic GitHub search.

Why does roadmap validation report DRIFT or STALE entries?▼

DRIFT means an entry fails the canonical format, links to a missing issue, or lacks the epic label. STALE means the linked issue was closed or reopened, so the entry sits in the wrong horizon. An explicit reformat operation repairs fixable entries.

What are the limitations of the roadmap curation skill?▼

It cannot file or close epic issues, edit anything outside the Epics block, sync automatically on a schedule, generate a roadmap from scratch, or aggregate across multiple repositories. Those tasks belong to the epic and epic-retrospective skills or manual processes.