Roadmap planning
Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.
npx -y skills add janellecipriano/pm-skills --skill roadmap-planningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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
Turn goals, themes, and initiatives into a structured product roadmap — now/next/later or quarterly — with outcomes, rough sizing, dependencies, and confidence. Use when the user says "build a roadmap", "plan the quarter/half/year", "prioritize our initiatives", "what should we work on next", or needs to sequence work against objectives.
SKILL.md
2.0 KB, as published. Nobody here has run it
Roadmap Planning
Translate strategy into a sequenced, outcome-oriented roadmap that communicates what, why, and roughly when — without overpromising dates.
When to use
- Planning a quarter/half/year, or refreshing an existing roadmap.
- Prioritizing and sequencing a backlog of initiatives against goals.
Inputs to gather
- The objectives/strategy the roadmap serves (link to OKRs if they exist — see
okr-tracking). - Candidate initiatives/themes and any known sizing, dependencies, or hard dates.
- The audience and horizon (internal team vs. external; quarterly vs. now/next/later).
Process
- Anchor each initiative to an objective and a target outcome — drop work that maps to nothing.
- Choose a format: Now / Next / Later (theme-based, low date commitment) or timeline/quarterly (when dates matter).
- For each item: state the outcome/problem, rough size (T-shirt or weeks), confidence (H/M/L), and dependencies.
- Prioritize with a clear lens (impact vs. effort, RICE, or value vs. risk) and make the rationale visible.
- Sequence respecting dependencies and capacity (sanity-check against
capacity-planning). - Note assumptions and what would change the plan. Distinguish committed vs. exploratory.
Output format
Default to a Now/Next/Later table unless dates are required:
## Now (this quarter)
| Initiative | Objective | Outcome | Size | Confidence | Dependencies |
## Next
...
## Later
...
Close with prioritization rationale and key assumptions/risks. Avoid precise dates for low-confidence items — use ranges or horizons.