SkillAgentSearch skills...

opportunity-solution-tree

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill opportunity-solution-tree

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Tags

Our assessment of opportunity-solution-tree

opportunity-solution-tree scores 92/100 on our quality scale, 13th of 60 Product Management skills we index (top 22%).

Its SKILL.md is 18 KB long, well organised into 38 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
18/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so opportunity-solution-tree is actively maintained.
  • Our last check on 2026-10-05 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

opportunity-solution-tree compared with similar skills

All 4 of these similar skills score higher than opportunity-solution-tree; compare them before choosing.

SkillScoreStarsUpdatedFormat
opportunity-solution-tree (this skill)by deanpeters927.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install opportunity-solution-tree?
Run npx skills add deanpeters/Product-Manager-Skills --skill opportunity-solution-tree. The install tabs above show the steps for each supported agent.
Which AI agents does opportunity-solution-tree work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is opportunity-solution-tree safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is opportunity-solution-tree still maintained?
The repository was last updated about 3 months ago, so opportunity-solution-tree is actively maintained.

name: opportunity-solution-tree argument-hint: "[stakeholder request or outcome]" description: Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build. intent: >- Guide product managers through creating an Opportunity Solution Tree (OST) by extracting target outcomes from stakeholder requests, generating opportunity options (problems to solve), mapping potential solutions, and selecting the best proof-of-concept (POC) based on feasibility, impact, and market fit. Use this to move from vague product requests to structured discovery, ensuring teams solve the right problems before jumping to solutions—avoiding "feature factory" syndrome and premature convergence on ideas. type: interactive theme: discovery-research best_for:

  • "Turning a stakeholder feature request back into a problem worth solving"
  • "Connecting a desired outcome to opportunities, solutions, and tests"
  • "Showing why one solution was chosen over the alternatives" scenarios:
  • "A stakeholder asked for a specific feature and I want to reframe it as a problem first"
  • "I need to show leadership why we picked this solution over the three alternatives" estimated_time: "30-45 min"

Purpose

Guide product managers through creating an Opportunity Solution Tree (OST) by extracting target outcomes from stakeholder requests, generating opportunity options (problems to solve), mapping potential solutions, and selecting the best proof-of-concept (POC) based on feasibility, impact, and market fit. Use this to move from vague product requests to structured discovery, ensuring teams solve the right problems before jumping to solutions—avoiding "feature factory" syndrome and premature convergence on ideas.

This is not a roadmap generator—it's a structured discovery process that outputs validated opportunities with testable solution hypotheses.

Input

Works best with: The stakeholder request or the target outcome you're starting from. Also useful: Customer evidence you already have, constraints, and solutions already being pushed.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The skill opens by asking for the request or desired outcome, then extracts the measurable target outcome from it.

Example invocation: Build an OST from this request: 'Sales says we need a mobile app because competitors have one.'

Key Concepts

What is an Opportunity Solution Tree (OST)?

An OST is a visual framework (Teresa Torres, Continuous Discovery Habits) that connects:

  1. Desired Outcome (business goal or product metric)
  2. Opportunities (customer problems, needs, pain points, or desires that could drive the outcome)
  3. Solutions (ways to address each opportunity)
  4. Experiments (tests to validate solutions)

Structure:

         Desired Outcome (1)
                |
    +-----------+-----------+
    |           |           |
Opportunity  Opportunity  Opportunity (3)
    |           |           |
  +-+-+       +-+-+       +-+-+
  | | |       | | |       | | |
 S1 S2 S3    S1 S2 S3    S1 S2 S3 (9 total solutions)

Why This Works

  • Outcome-driven: Starts with business goal, not feature requests
  • Divergent before convergent: Explores multiple opportunities before picking solutions
  • Problem-focused: Opportunities are problems, not solutions disguised as problems
  • Testable: Each solution maps to experiments, not just "build it and ship"
  • POC selection: Evaluates feasibility, impact, market fit before committing resources

Anti-Patterns (What This Is NOT)

  • Not a feature list: Opportunities are problems customers face, not "we need dark mode"
  • Not solution-first: Don't start with "we should build X"—start with "customers struggle with Y"
  • Not waterfall planning: OST is a discovery tool, not a project plan
  • Not a one-time exercise: OSTs evolve as you learn from experiments

When to Use This

  • Stakeholder requests a feature or product initiative
  • Starting discovery for a new product area
  • Clarifying vague OKRs or strategic goals
  • Prioritizing which problems to solve first
  • Aligning team on what outcomes you're driving

When NOT to Use This

  • When the problem is already validated (move to solution testing)
  • For tactical bug fixes or technical debt (no discovery needed)
  • When stakeholders demand a specific solution (address alignment issues first)

Facilitation Source of Truth

Use workshop-facilitation as the default interaction protocol for this skill.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

Use template.md for the full fill-in structure.

This interactive skill follows a two-phase process:

Phase 1: Generate OST (extract outcome, identify opportunities, map solutions) Phase 2: Select POC (evaluate solutions, recommend best starting point)


Step 0: Gather Context (Before Questions)

Agent suggests:

Before we create your Opportunity Solution Tree, let's gather context:

Stakeholder Request or Product Initiative:

  • What did the stakeholder ask for? (Feature request, product idea, strategic goal)
  • Any existing materials: PRD drafts, OKR documents, strategy memos, meeting notes
  • Problem statements, customer complaints, or research findings

Product Context (if available):

  • Website copy, positioning statements, product descriptions
  • Competitor materials, customer reviews (G2, Capterra), community discussions
  • Usage data, support tickets, churn reasons

You can paste this content directly, or describe the request briefly.


Phase 1: Generate Opportunity Solution Tree

Question 1: Extract Desired Outcome

Agent asks: "What's the desired outcome for this initiative? (What business or product metric are you trying to move?)"

Offer 4 enumerated options:

  1. Revenue growth — "Increase ARR, expand revenue from existing customers, new revenue streams" (Common for scaling products)
  2. Customer retention — "Reduce churn, increase activation, improve engagement/stickiness" (Common for established products with retention issues)
  3. Customer acquisition — "Increase sign-ups, trial conversions, new user growth" (Common for early-stage or growth products)
  4. Product efficiency — "Reduce support costs, decrease time-to-value, improve operational metrics" (Common for mature products optimizing operations)

Or describe your specific desired outcome (be measurable: e.g., "Increase trial-to-paid conversion from 15% to 25%").

User response: [Selection or custom]

Agent extracts and confirms:

  • Desired Outcome: [Specific, measurable outcome]
  • Why it matters: [Rationale from stakeholder request or context]

Question 2: Identify Opportunities (Problems to Solve)

Agent generates 3 opportunities based on the desired outcome and context provided.

Agent says: "Based on your desired outcome ([from Q1]) and the context you provided, here are 3 opportunities (customer problems or needs) that could drive this outcome:"

Example (if Outcome = Increase trial-to-paid conversion):

  1. Opportunity 1: Users don't experience value during trial — "New users sign up but don't complete onboarding, never reach 'aha moment,' abandon before seeing core value"

    • Evidence: [From context: onboarding analytics, support tickets, exit surveys]
  2. Opportunity 2: Pricing is unclear or misaligned — "Users unsure if paid plan is worth it; don't understand what they get for the price; pricing page confusing"

    • Evidence: [From context: conversion funnel drop-off at pricing page, sales objections]
  3. Opportunity 3: Free plan is 'good enough' — "Users stay on free tier indefinitely because it meets their needs; no compelling reason to upgrade"

    • Evidence: [From context: freemium user retention data, support tickets asking for workarounds]

Agent asks: "Which opportunity feels most critical to explore first, or would you like to modify/add opportunities?"

User response: [Selection or custom]


Question 3: Generate Solutions for Selected Opportunity

Agent generates 3 solution ideas for the selected opportunity.

Agent says: "For Opportunity [X]: [Name], here are 3 potential solutions to test:"

Example (if Opportunity 1 selected: Users don't experience value during trial):

  1. Solution 1: Guided onboarding checklist — "Interactive checklist that walks users through core workflows step-by-step (e.g., 'Create your first project,' 'Invite a teammate,' 'Complete a task')"

    • Hypothesis: Structured guidance increases completion rate
    • Experiment: A/B test checklist vs. no checklist, measure activation rate
  2. Solution 2: Time-to-value triggers — "Automatically prompt users when they're stuck (e.g., 'You haven't created a project yet—here's a template to get started')"

    • Hypothesis: Proactive nudges prevent drop-off
    • Experiment: Track engagement with prompts, measure trial-to-paid lift
  3. Solution 3: Human-assisted onboarding — "Offer 15-min onboarding call with CSM for high-value trial users (enterprise, team plans)"

    • Hypothesis: Personal touch increases conversion for high-intent users
    • Experiment: Offer to 50 trial users, measure conversion vs. control group

Agent asks: "Would you like to explore solutions for another opportunity, or move to POC selection?"

User response: [Selection or custom]


Phase 2: Select Proof-of-Concept (POC)

After generating solutions, the agent helps select which solution to test first.


Question 4: Evaluate Solutions (Feasibility, Impact, Market Fit)

Agent says: "Let's evaluate your solutions to pick the best starting point. I'll score each solution on Feasibility (how hard to build), Impact (how much it could move the outcome), and Market Fit (how well it aligns with customer needs)."

Agent generates evaluation table:

| Solution | Feasibility (1-5) | Impact (1-5) | Market Fit (1-5) | Total Score | Rationale | |----------|-------------------|--------------|------------------|-------------|-----------| | Solution 1: Guided onboarding checklist | 4 | 4 | 5 | 13 | High feasibility (UI pattern), proven impact (industry standard), strong market fit (users expect onboarding) | | Solution 2: Time-to-value triggers | 3 | 3 | 4 | 10 | Medium feasibility (requires analytics integration), moderate impact (depends on trigger quality), good market fit | | Solution 3: Human-assisted onboarding | 5 | 5 | 3 | 13 | High feasibility (no dev work), high impact (personal touch), lower market fit (doesn't scale, high-touch only) |

Scoring criteria:

  • Feasibility: 1 = months of work, 5 = days/weeks
  • Impact: 1 = minimal outcome movement, 5 = major outcome shift
  • Market Fit: 1 = customers don't care, 5 = customers actively request this

Agent recommends:

Recommended POC: Solution 1 (Guided onboarding checklist)

Why this POC:

  • Balances feasibility (can build in 2-4 weeks) with impact (proven pattern)
  • Strong market fit (users expect onboarding guidance)
  • Testable hypothesis: "If we guide users through core workflows, activ

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProduct
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium