New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Opportunity Solution Tree

by phuryn in phuryn/pm-skills

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.

MITAuto-check passedProduct & Project Management

Install Opportunity Solution Tree

skills CLI
$ npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install phuryn/pm-skills opportunity-solution-tree --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-product-discovery/skills/opportunity-solution-tree .claude/skills/opportunity-solution-tree && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
opportunity-solution-tree
GitHub stars
27k
Token cost
~1.1k tokens
SKILL.md length
480 words
Files
1
Skills in repo
60
Repo updated
First seen
Licence
MIT

At a glance

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.

  • Works in 4 steps: Desired Outcome (top) — The measurable… → Opportunities (second level) — Customer… → Solutions (third level) — Possible ways… → …
  • Structuring discovery work
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Mapping opportunities to solutions

What it does

Opportunity Solution Tree is an agent skill from phuryn/pm-skills. Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.

When your agent uses it

  • Structuring discovery work
  • Mapping opportunities to solutions
  • Deciding what to build next

Example prompts

  • “/opportunity-solution-tree”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Desired Outcome (top) — The measurable business or product outcome the team is pursuing. Should be a single, clear metric (e.g., "increase…
  2. Opportunities (second level) — Customer needs, pain points, or desires discovered through research. These are problems worth solving — not…
  3. Solutions (third level) — Possible ways to address each opportunity. Generate multiple solutions per opportunity — don't commit to the…
  4. Experiments (bottom) — Fast, cheap tests to validate whether a solution actually addresses the opportunity. Use assumption testing (Value…

What it can do on your machine

Read from SKILL.md and the folder at commit 8607e3b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • productcompass.pm

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Opportunity Solution Tree loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 480 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from phuryn/pm-skills at commit 8607e3b, republished under its MIT licence (© phuryn). 480 words, ~1,063 tokens.

Download SKILL.mdSave it as .claude/skills/opportunity-solution-tree/SKILL.md (or your agent's skills folder).
name
opportunity-solution-tree
description
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.

Opportunity Solution Tree (OST)

A visual framework for structuring continuous product discovery. Connects a desired outcome to customer opportunities, possible solutions, and experiments to validate them.

Domain Context

The Opportunity Solution Tree (Teresa Torres, Continuous Discovery Habits) is the backbone of modern product discovery. It prevents teams from jumping to solutions by forcing them to first map the opportunity space.

Structure (4 levels):

  1. Desired Outcome (top) — The measurable business or product outcome the team is pursuing. Should be a single, clear metric (e.g., "increase 7-day retention to 40%"). This comes from your OKRs or product strategy.

  2. Opportunities (second level) — Customer needs, pain points, or desires discovered through research. These are problems worth solving — not features. Frame them from the customer's perspective: "I struggle to..." or "I wish I could..." Prioritize using Opportunity Score: Importance × (1 − Satisfaction) (Dan Olsen, The Lean Product Playbook). Normalize Importance and Satisfaction to 0–1.

  3. Solutions (third level) — Possible ways to address each opportunity. Generate multiple solutions per opportunity — don't commit to the first idea. The Product Trio (PM + Designer + Engineer) should ideate together. "Best ideas often come from engineers."

  4. Experiments (bottom) — Fast, cheap tests to validate whether a solution actually addresses the opportunity. Use assumption testing (Value, Usability, Viability, Feasibility risks). Prefer experiments with "skin-in-the-game" (Alberto Savoia) over opinion-based validation.

Key principles:

  • One outcome at a time. Don't try to solve everything. Focus the tree on a single desired outcome.
  • Opportunities, not features. "Never allow customers to design solutions. Prioritize opportunities (problems), not features."
  • Compare and contrast. Always generate at least 3 solutions per opportunity before choosing. Avoid the "first idea" trap.
  • Discovery is not linear. Loop back if experiments fail. Kill solutions that don't validate. Explore new branches.
  • Continuous, not periodic. Update the tree weekly as you learn from interviews, analytics, and experiments.
Show full SKILL.md (178 more words)Show less
Instructions

You are helping a product team build an Opportunity Solution Tree for $ARGUMENTS.

Input Requirements
  • A desired outcome or business metric to improve
  • Customer research data (interviews, surveys, analytics, feedback)
  • Optionally: existing opportunities or solution ideas to organize
Process

  1. Define the desired outcome — Confirm or help articulate a single, measurable outcome at the top of the tree.

  2. Map opportunities — From provided research, identify 3-7 customer opportunities (needs/pains). Group related opportunities. Frame each from the customer's perspective.

  3. Prioritize opportunities — Use Opportunity Score or qualitative assessment to rank. Focus on the top 2-3.

  4. Generate solutions — For each prioritized opportunity, brainstorm 3+ solutions from PM, Designer, and Engineer perspectives.

  5. Design experiments — For the most promising solutions, suggest 1-2 fast experiments. Specify: hypothesis, method, metric, success threshold.

  6. Visualize the tree — Present the full OST in a clear hierarchical format.

Think step by step. Save as markdown if substantial.

Further Reading

© phuryn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in pm-product-discovery/skills/opportunity-solution-tree of phuryn/pm-skills.

Open the folder on GitHubat commit 8607e3b

Compare with similar skills

Opportunity Solution Tree next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Opportunity Solution Tree compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Opportunity Solution Tree this skillphuryn/pm-skills27k—~1.1kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Self Improving Agent

    farm-fe/farm

    A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from phuryn/pm-skills

All 60 skills in this repo

  • Agreement-Based Code Review

    phuryn/pm-skills

    Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.

    27k GitHub stars~3.6k tokensUpdated 23 days ago
    Auto-check passed

  • A/B Test Analysis

    phuryn/pm-skills

    Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.

    27k GitHub stars~893 tokensUpdated 23 days ago
    Auto-check passed

  • Team OKR Brainstorm

    phuryn/pm-skills

    Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.

    27k GitHub stars~1.1k tokensUpdated 23 days ago
    Auto-check passed

  • Cohort Analysis and Retention Explorer

    phuryn/pm-skills

    Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.

    27k GitHub stars~1.3k tokensUpdated 23 days ago
    Auto-check passed

  • Dummy Dataset Generator

    phuryn/pm-skills

    Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.

    27k GitHub stars~983 tokensUpdated 23 days ago
    Auto-check passed

  • Grammar and Flow Checker

    phuryn/pm-skills

    Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.

    27k GitHub stars~2.4k tokensUpdated 23 days ago
    Auto-check passed

Categories

Questions about Opportunity Solution Tree

What does Opportunity Solution Tree do?

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Opportunity Solution Tree is an agent skill from phuryn/pm-skills. Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.

When should I use Opportunity Solution Tree?

Opportunity Solution Tree fits situations like: structuring discovery work; mapping opportunities to solutions; deciding what to build next.

How do I install Opportunity Solution Tree in Claude Code?

Run `npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a claude-code`. Or copy the skill folder (pm-product-discovery/skills/opportunity-solution-tree in phuryn/pm-skills) into .claude/skills/opportunity-solution-tree in your project. Claude Code loads it when a task matches its description.

How do I install Opportunity Solution Tree in Codex?

Run `npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a codex`. Or copy the skill folder (pm-product-discovery/skills/opportunity-solution-tree in phuryn/pm-skills) into .agents/skills/opportunity-solution-tree in your project. Codex loads it when a task matches its description.

Can I use Opportunity Solution Tree in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opportunity-solution-tree, .gemini/skills/opportunity-solution-tree, .github/skills/opportunity-solution-tree and .opencode/skills/opportunity-solution-tree in your project.

What does Opportunity Solution Tree need to run?

SKILL.md names no scripts, command-line tools or credentials: Opportunity Solution Tree is instructions for the agent only.

Does Opportunity Solution Tree access the network?

SKILL.md names 1 domain. As links in the text: productcompass.pm. This is read from the text; nothing was executed.

Is Opportunity Solution Tree safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Opportunity Solution Tree use?

Opportunity Solution Tree is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Opportunity Solution Tree use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Opportunity Solution Tree?

Skills that share tags, products or a category with Opportunity Solution Tree: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Opportunity Solution Tree?

phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,825 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on September 14, 2026.

Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.