A facilitated thinking exercise: look back at what happened, then look forward to set strategic direction — before building the tactical roadmap.
/strategic-roadmap-review1-2 days → 45 min
Compared to doing it manually
/strategic-roadmap-reviewType this in Claude to run the skill
Most PMs jump straight into "what should we build next?" without honestly assessing what happened. Previous roadmap items quietly disappear, customer learnings get ignored, and the result is roadmaps disconnected from reality that repeat past mistakes.
.claude/skills/ folder in your project/strategic-roadmap-review in Claude to run the skill/prioritization-engineScore and rank features using RICE, ICE, or weighted scoring with clear documentation.
/north-star-finderIdentify and validate your product's North Star metric with supporting input metrics.
/go-to-market-strategyCreates a complete GTM plan with channels, messaging, timeline, and success metrics
/value-proposition-canvasCreates a Value Proposition Canvas mapping customer needs to product value
A structured exercise where you assess what happened before planning what's next. You review business health, product health, customer learnings, and your previous roadmap's results — then use those findings to set business objectives, product outcomes, and strategic initiatives for the next period.
Sprint retros focus on team process at the execution level. A strategic roadmap review operates at the planning level — it assesses whether you pursued the right objectives, whether your product bets paid off, and what customer evidence should shape the next period. It feeds into roadmap planning, not sprint planning.
Most teams skip this and repeat the same mistakes — over-scoping, ignoring capacity constraints, or quietly dropping commitments. Reviewing what shipped, what didn't, and why creates accountability and surfaces patterns that make the next roadmap more realistic.
Two categories: items you're deferring (right idea, wrong time) and items you're declining (wrong direction for your strategy). Each should include the rationale and when to revisit. This prevents scope creep and arms you with clear answers when stakeholders ask "what about X?"
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.