roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
Profile →npx skills add rampstackco/claude-skills --skill roadmap-planning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Roadmap Planning Take a pile of ideas, requests, and ongoing work. Produce a defensible plan for what to ship, when, and why. The output is a roadmap document plus the prioritization work that made it credible. --- ## When to use - Planning the next quarter or the next year - Sequencing work where some items depend on others - Balancing new builds, improvements, and maintenance - Saying no (or "not yet") to specific requests with a defensible reason - Aligning a team around a single shared plan - Communicating the plan to stakeholders outside the team - Replanning after a strategy shift, a missed quarter, or new constraints ## When NOT to use - Specifying a single feature for development (use `pm-spec-writing`) - Validating whether the idea is worth building (use `ux-research`) - Designing the feature itself (use `design-standards`) - Writing the launch plan for a single initiative (use `launch-runbook`) - Reviewing what shipped vs what was promised (use `after-action-report`) --- ## Required inputs - The team's strategy or top-level goals (1 to 5 OKRs, themes, or pillars) - The backlog: every candidate item, with at least a one-sentence description - The team's capacity (people
- When to use
- When NOT to use
- Required inputs
- The framework: 5 layers
- Layer 1: Themes (the WHY)
- Layer 2: Initiatives (the WHAT)
- Layer 3: Sequencing (the WHEN)
- Layer 4: Capacity reality (the HOW MUCH)
- Layer 5: Trade-off communication (the WHY NOT)
- Workflow
- Step 1: Anchor the strategy
- Step 2: Catalog the backlog
- Step 3: Prioritize within each theme
- Step 4: Build the dependency map
What does the roadmap-planning skill do?
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill roadmap-planning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.