agentsclimarketplace

Build portfolio roadmap strategy

Skill alexe-ev/product-plugins/product-strategy/skills/build-portfolio-roadmap-strategy

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-portfolio-roadmap-strategy

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

Structure product portfolio decisions and translate strategy into a prioritized roadmap. Use this skill when a team needs to align investment decisions with strategic goals and build a coherent roadmap.

SKILL.md

2.8 KB, 529 tokens by cl100k_base, as published. Nobody here has run it

Build Portfolio & Roadmap Strategy

Purpose

Help teams translate product strategy and business goals into a structured portfolio view and a prioritized roadmap that reflects strategic trade-offs.

Skill type

Conceptual skill

Use this skill when

  • A team needs to prioritize across multiple product areas or bets
  • A roadmap exists but lacks strategic coherence
  • Leadership needs to make investment trade-off decisions across the portfolio
  • The team is planning for a new quarter, half, or year

Do not use this skill when

  • A single feature needs prioritization (this skill is portfolio-level, not feature-level)
  • The team needs vision definition (use define-product-vision)
  • The team needs delivery planning and sprint-level execution (use product-planning skills)

Required inputs

  • Current product areas or bets (even rough list)
  • Business goals or strategic priorities
  • Any constraints (team size, budget, timeline)

Optional inputs

  • Existing roadmap or backlog
  • Customer segment priorities
  • Product-market fit assessment per area
  • Competitive context
  • OKRs or KPIs

Upstream context

Works best when:

  • Product vision is defined
  • Key strategic bets are identified
  • Business goals or OKRs exist

If upstream context is missing

If no strategic goals or product areas are provided, produce a portfolio structuring framework first. Do not prioritize without knowing what the goals are.

Downstream handoff

Output can feed:

  • product-planning domain (translate portfolio decisions into roadmap execution)
  • define-success-metrics (assign metrics to each portfolio bet)

Instructions

  1. Identify all current product areas, bets, or investment themes.
  2. Map each area to a strategic goal or business outcome.
  3. Assess relative strategic priority: core / growth / explore.
  4. Identify resource constraints and trade-offs.
  5. Produce a portfolio view with rationale.
  6. Produce a high-level roadmap structure (now / next / later or similar framework).
  7. List assumptions and decisions that require stakeholder alignment.

Output

Provide:

  • Portfolio map: areas and their strategic classification
  • Prioritization rationale
  • High-level roadmap structure (now / next / later)
  • Trade-offs and what is being deprioritized and why
  • Key alignment decisions needed
  • Confidence level: provisional / context-informed / ready-to-present

Risks / caveats

  • Do not build a roadmap without knowing the strategic goals
  • Prioritization without trade-off visibility creates false clarity
  • A roadmap is a communication tool, not a commitment — label it accordingly

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.