Agent skill

opportunity-solution-tree

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.

deanpetersgithub.com/deanpetersGitHub ↗
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill opportunity-solution-tree --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 17 KB
Bundled scripts: none
Path: skills/opportunity-solution-tree/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,255
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## 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

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. What is an Opportunity Solution Tree (OST)?
  5. Why This Works
  6. Anti-Patterns (What This Is NOT)
  7. When to Use This
  8. When NOT to Use This
  9. Facilitation Source of Truth
  10. Application
  11. Step 0: Gather Context (Before Questions)
  12. Phase 1: Generate Opportunity Solution Tree
  13. Question 1: Extract Desired Outcome
  14. Question 2: Identify Opportunities (Problems to Solve)
Ships with 2 files
  • examples/sample.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the opportunity-solution-tree skill do?

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.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill opportunity-solution-tree --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 deanpeters/Product-Manager-Skills, a repository with 6,255 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.

Keep going