Strategic product roadmap planning
Turn strategy into an outcome-driven roadmap — gather inputs, define epic hypotheses, prioritize, sequence by quarter, communicate to stakeholders
- What
- Turn strategy into an outcome-driven roadmap — gather inputs, define epic hypotheses, prioritize, sequence by quarter, communicate to stakeholders
- Cost
- Free
- Needs
- nothing — the workflow is guidance; bring the product name and planning horizon (next quarter, next year), plus strategy/OKRs, candidate initiatives, team capacity and known stakeholder pressures if you have them
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @deanpeters's guided roadmap-planning workflow for product managers — 5 phases over 1–2 weeks: gather inputs (OKRs, customer problems, technical constraints, stakeholder requests), define epics as hypotheses with success metrics and T-shirt effort estimates, prioritize with RICE/ICE plus strategic overrides, sequence into Now/Next/Later quarters with dependency mapping and engineering validation, then present, gather feedback and publish — with a facilitation protocol (guided / context-dump / best-guess entry modes), numbered recommendations, and anti-patterns called out (feature factories, HiPPO prioritization, roadmap-as-contract waterfall thinking). Orchestrates companion component skills (epic-hypothesis, prioritization-advisor) that live in the same repository — install the whole repo. Honest caveats: license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing — the workflow is guidance; bring the product name and planning horizon (next quarter, next year), plus strategy/OKRs, candidate initiatives, team capacity and known stakeholder pressures if you have them Install "Strategic product roadmap planning" for me. It gives the agent @deanpeters's 5-phase roadmap workflow: gather inputs (business goals, customer problems, technical constraints, stakeholder requests), define epics as hypotheses with success metrics and effort estimates, prioritize with RICE/ICE and strategic adjustments, sequence by quarter with dependency mapping, and present to stakeholders. IMPORTANT: the repo states no license — fetch and install the whole repository (it also contains the companion skills epic-hypothesis and prioritization-advisor that the workflow orchestrates), and reproduce nothing beyond the link. Repository: https://github.com/deanpeters/product-manager-skills/blob/main/skills/roadmap-planning/SKILL.md 1. Fetch the SKILL.md file (and its companion component skills from the same repository) into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the files for anything suspicious. This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy the skill files into the agent's skills directory, in a folder named "roadmap-planning". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. give the agent my product, horizon, OKRs and candidate initiatives to start Phase 1). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.