plan-roadmap
The plan-roadmap command transforms strategic initiatives into a sequenced delivery roadmap by building planning context, converting initiatives into testable hypotheses, applying prioritization frameworks, and mapping user stories while identifying dependencies and sequencing risks. Use this when translating validated opportunities and strategy into concrete quarterly or release plans with clear tradeoffs and outcome linkages.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/deanpeters/Product-Manager-Skills/HEAD/commands/plan-roadmap.md -o ~/.claude/commands/plan-roadmap.mdplan-roadmap.md
# /plan-roadmap Create a roadmap that reflects strategy, risk, and delivery reality. ## Invocation ```text /plan-roadmap Q3-Q4 plan for enterprise reporting and permissions ``` ## Workflow 1. Build roadmap context with `roadmap-planning`. 2. Convert initiatives into `epic-hypothesis` statements. 3. Select the right framework via `prioritization-advisor`. 4. Create delivery slices with `user-story-mapping`. 5. Break oversized epics with `epic-breakdown-advisor`. ## Checkpoints - Ensure every roadmap item ties to an explicit outcome. - Expose why items are not being prioritized. - Capture dependencies and sequencing risk. ## Next Steps - Run `/write-prd` for the top roadmap slice. - Run `/discover` for high-uncertainty initiatives.
Run a structured discovery flow from problem framing through opportunity mapping and validation planning.
Guide PM to Director to VP/CPO transition planning with role-fit diagnostics and onboarding guidance.
Select what to work on next using the right prioritization method for your context.
Build product strategy from positioning through opportunity and roadmap decisions.
Create a decision-ready PRD by chaining problem framing, requirements definition, and story scaffolding.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.