roadmap-planning
by deanpetersThe roadmap-planning skill helps product managers turn goals, requests, and constraints into a defensible roadmap with prioritization, epic definition, stakeholder alignment, and sequencing. It is useful for roadmap-planning for Product Management when you need a clear narrative for now, next, and later.
This skill scores 83/100, which means it is a solid listing candidate for directory users who want a structured roadmap-planning workflow rather than a generic prompt. The repository gives enough clarity to decide that it is installable and likely to reduce guesswork for strategic roadmap creation, though it lacks supporting files and install-time aids that would make adoption even easier.
- Strong triggerability: the frontmatter clearly defines when to use it, with scenarios like Q2 planning, 6-month roadmaps, and exec review.
- Operational workflow value: the skill body is substantial, with explicit roadmap planning phases covering prioritization, epic definition, stakeholder alignment, sequencing, and communication.
- Good install decision evidence: includes a roadmap template and worked examples showing outcome-driven planning versus a weak feature-list approach.
- No install command, scripts, or support files, so users must rely on the markdown guidance alone.
- The repository references other skills (for example, prioritization-advisor.md), which may add dependency-like context that is not bundled here.
Overview of roadmap-planning skill
The roadmap-planning skill helps product managers turn scattered requests, goals, and constraints into a strategic roadmap that can survive stakeholder review. It is best for teams that need more than a feature list: they need sequencing, tradeoff logic, and a clear narrative for why items land now, next, or later. If you are doing roadmap-planning for Product Management, this skill is aimed at that handoff from strategy to execution.
What roadmap-planning is for
Use this skill when you already have inputs like OKRs, customer pain points, dependencies, and rough initiative ideas, but need a coherent release plan. The job-to-be-done is to prioritize work, define epics at the right level, and align the roadmap to outcomes rather than output. That makes the roadmap easier to defend in exec conversations and easier for delivery teams to execute.
When this skill is a strong fit
The roadmap-planning skill fits annual planning, quarterly planning, and cross-team sequencing where choices matter more than volume. It is especially useful when multiple stakeholders are asking for different things and you need a disciplined way to decide what ships first. If your main problem is “we have too many ideas,” this is a better fit than a generic prompt.
What makes it different
This workflow emphasizes strategic framing, not just formatting. It pushes you to connect initiatives to customer problems, business goals, and dependencies so the roadmap tells a story. The result is usually more credible than a simple prioritization table because it includes the logic behind the order of work.
How to Use roadmap-planning skill
Install roadmap-planning
Install the roadmap-planning skill with the repository’s skill command:
npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning
After install, start with skills/roadmap-planning/SKILL.md because it defines the workflow intent, best-fit scenarios, and expected planning sequence. Then read template.md for the output structure and examples/sample.md for a realistic good-vs-bad comparison.
Feed it the right inputs
The roadmap-planning usage pattern works best when you supply concrete inputs, not a vague “make me a roadmap.” Give it:
- business goals or OKRs
- target customer segment
- candidate initiatives or epics
- known dependencies and constraints
- time horizon, such as quarter or half-year
- any stakeholder positions that may affect tradeoffs
A weak prompt says: “Plan our roadmap.” A stronger one says: “Plan a Q2 roadmap for SMB onboarding and retention, using our goals to reduce churn from 15% to 8%, with 8 candidate initiatives, 2 engineering constraints, and a need to show executive tradeoffs.”
Suggested workflow and files
Use the skill as a planning assistant, then validate the output against your own product context. A practical workflow is:
- Collect goals, customer problems, and constraints.
- Draft candidate epics and group related work.
- Ask the skill to prioritize and sequence by outcome.
- Check whether the roadmap narrative matches stakeholder reality.
- Revise for feasibility, dependency order, and communication clarity.
If you are scanning the repo, preview SKILL.md, template.md, and examples/sample.md first. Those files show the expected shape of the roadmap, the level of abstraction, and how the skill distinguishes a strategic roadmap from a backlog dump.
Tips that improve output quality
Be explicit about what must be protected, what can move, and what is still uncertain. The roadmap-planning guide works better when you name hard constraints like launch windows, team capacity, or blocked dependencies. Also tell it whether the roadmap is internal, exec-facing, or customer-facing, because the communication style and level of detail should change.
roadmap-planning skill FAQ
Is roadmap-planning only for Product Management?
It is designed for roadmap-planning for Product Management, but adjacent roles can use it if they need a structured release plan. It is strongest when someone owns prioritization and stakeholder alignment, not just task tracking. If you are only creating an engineering sprint plan, this skill is usually too strategic.
How is this different from a normal prompt?
A normal prompt can draft a roadmap, but this skill gives you a repeatable workflow for prioritization, epic definition, sequencing, and communication. That reduces the chance of ending up with a feature list that lacks rationale. In practice, the roadmap-planning skill is better when you need consistency across planning cycles.
Is it beginner-friendly?
Yes, if you can provide basic product context. You do not need a fully polished strategy document to start; the skill is meant to help you organize rough inputs into a defensible roadmap. Beginners will get better results if they use the template and include explicit goals and constraints.
When should I not use it?
Do not use it when you need a detailed delivery plan, a release checklist, or a purely technical implementation sequence. It is also a poor fit if your inputs are too incomplete to support tradeoffs. In those cases, gather more context first or use a narrower planning prompt.
How to Improve roadmap-planning skill
Give better decision inputs
The fastest way to improve roadmap-planning results is to improve the quality of the inputs you give the model. Include customer evidence, goal metrics, and the handful of initiatives you are truly considering. If you only provide a wish list, the output will tend to mirror that list instead of making hard choices.
State tradeoffs and constraints early
The roadmap-planning skill works best when the prompt names what cannot happen. Tell it about capacity limits, strategic bets, technical dependencies, or stakeholder commitments that affect sequencing. This helps the output avoid unrealistic “everything now” planning and makes the roadmap easier to defend.
Ask for the format you will actually use
If you need an exec-ready roadmap, ask for a concise narrative plus now/next/later structure. If you need planning support, ask for rationale, risks, and dependency notes. The roadmap-planning guide is most useful when the output format matches the decision you are making, not when it is overformatted for its own sake.
Iterate after the first draft
Treat the first output as a planning draft, not the final answer. Review whether the priorities reflect your actual strategy, whether epics are too broad or too narrow, and whether sequencing respects dependencies. Then rerun roadmap-planning with corrections like “move enterprise SSO earlier,” “split reporting into two epics,” or “optimize for retention over expansion this quarter.”