Roadmap

Skill gmarmat/claude-pm-kit/.claude/skills/roadmap

PM Twin — your digital peer product manager. Claude Code skills for the full product lifecycle: discovery, validation, planning, building, productizing, launching, growing.

Install

npx -y skills add gmarmat/claude-pm-kit --skill roadmap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

[PM Twin] Generate or update product roadmap from PRD phases and feature index.

SKILL.md

2.2 KB, as published. Nobody here has run it

Roadmap — Product Roadmap Generator

Generate a visual product roadmap from PRD phases and arch.md feature index.

Execution Steps

Read PRD — Extract phases, features, priorities (P0/P1/P2), timelines
Read arch.md — Feature index with current status (planned/in-progress/done)
Read git log — Recent commits to detect progress since last roadmap update
Generate roadmap — Organize by the requested view (quarter/month/sprint)
Save — docs/toolkit/roadmap.md (markdown) or docs/toolkit/roadmap.html (visual)

Output Format

Markdown (default)

## Roadmap — [Product Name]

### Sprint 1 (Current)
- [x] Feature A — done
- [ ] Feature B — in progress (60%)
- [ ] Feature C — planned

### Sprint 2
- [ ] Feature D — P0
- [ ] Feature E — P1

### Backlog
- Feature F — P2
- Feature G — P2

HTML (if requested)

Timeline visualization with:

Horizontal time axis (weeks/months/quarters)
Feature cards positioned by phase
Color coding by status (done/in-progress/planned)
Dependencies shown as connecting lines

Update Mode

When run with update:

Read existing roadmap
Compare with current arch.md feature index
Mark completed items, adjust timeline
Flag features that slipped or changed scope
Present diff to user for confirmation

Prerequisites

Check before running:

docs/PRD.md must exist — if missing: "Run /pm setup to create your PRD first."
docs/arch.md should exist for feature index — if missing, build from PRD phases only

Important Rules

Reflect reality — roadmap matches PRD + arch.md, not wishful thinking
Flag slippage — if features are behind, say so clearly
Keep it current — suggest running after each sprint/milestone
Check existing first — read docs/toolkit/roadmap.md before generating. Update it, don't recreate from scratch.
Write only to docs/toolkit/ — never modify application code