agentsclimarketplace

Build roadmap prioritization

Skill alexe-ev/product-plugins/product-planning/skills/build-roadmap-prioritization

Skill library for AI agents — 15 product domains, 121 skills. Tells the agent what to ask, how to reason, and what to output.

Install
npx -y skills add alexe-ev/product-plugins --skill build-roadmap-prioritization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build and prioritize a feature or initiative roadmap using structured frameworks. Use this skill when a team has a backlog or list of initiatives and needs a coherent, prioritized plan.

SKILL.md

2.5 KB, 500 tokens by cl100k_base, as published. Nobody here has run it

Build Roadmap & Prioritization

Purpose

Help teams structure and prioritize a product roadmap that reflects strategic goals, user value, and delivery constraints.

Skill type

Conceptual skill

Use this skill when

  • A team has a long backlog and can't decide what to do next
  • A roadmap exists but lacks strategic coherence or trade-off clarity
  • Stakeholders are debating priorities without a structured framework
  • A quarterly or annual roadmap planning cycle is starting

Do not use this skill when

  • The goal is portfolio-level strategy (use build-portfolio-roadmap-strategy)
  • The goal is sprint-level delivery planning (use plan-delivery-collaboration)

Required inputs

  • List of features, initiatives, or requests (even rough)
  • Goals or OKRs this roadmap should serve

Optional inputs

  • Prioritization criteria or weights
  • Team capacity or constraints
  • Customer segment priorities
  • Technical dependencies

Upstream context

Works best when:

  • Goals/OKRs are defined
  • Opportunities are framed and sized

If upstream context is missing

If no goals are defined, do not prioritize. First establish what outcomes the roadmap should drive.

Downstream handoff

Output can feed:

  • write-requirements-prd (define requirements for top priority items)
  • plan-delivery-collaboration (structure delivery for prioritized items)
  • set-goals-okrs-kpis (validate that prioritized items map to goals)

Instructions

  1. Collect all initiatives to be considered.
  2. Apply a prioritization framework (RICE, ICE, opportunity-impact, or goal-mapping).
  3. Map each initiative to a goal or OKR.
  4. Identify quick wins vs. strategic bets.
  5. Identify dependencies and sequencing constraints.
  6. Produce a now / next / later roadmap structure.
  7. Make trade-offs explicit: what is being deprioritized and why.

Output

Provide:

  • Prioritized initiative list with rationale
  • Roadmap structure (now / next / later or time-horizon based)
  • Goal mapping for each initiative
  • Trade-off decisions (what was deprioritized)
  • Dependencies and sequencing notes
  • Assumptions

Risks / caveats

  • Prioritization without goals is opinion sorting, not strategy
  • A roadmap is a communication tool, not a contract
  • Make deprioritization visible — hiding it creates misalignment

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.