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:
Quick answer
Strategic product roadmap planning is a free Muse skill offering a guided roadmap-planning workflow for product managers over five phases in one to two weeks. It gathers inputs like OKRs, customer problems, technical constraints and stakeholder requests, defines epics as hypotheses with success metrics and T-shirt effort estimates, prioritizes with RICE or ICE, then sequences by quarter and publishes.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 1b5a524Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/deanpeters/product-manager-skills/1b5a524ebb95e9497fa3f25002d8b8ec528d4444/skills/roadmap-planning/SKILL.md Pinned version: install the code at commit 1b5a524ebb95e9497fa3f25002d8b8ec528d4444 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and its companion component skills from the same repository) into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 1b5a524 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.