opportunity-solution-tree · phuryn — Claude Code skill: build an OST
A skill that builds an Opportunity Solution Tree: outcome, customer needs, solutions, experiments. Use it when structuring discovery work or deciding what to build next.
npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a claude-codeWhat opportunity-solution-tree does
The skill turns product discovery into a four-level tree, following Teresa Torres' Continuous Discovery Habits. Top level is one measurable outcome, like "increase 7-day retention to 40%". Below it sit customer opportunities — needs and pains framed as "I struggle to..." or "I wish I could...". Then solutions, at least three per opportunity, and at the bottom cheap experiments to validate them.
It walks through six steps: define the outcome, map 3–7 opportunities from research, prioritize them with Opportunity Score (Importance × (1 − Satisfaction)), brainstorm solutions from PM, designer and engineer perspectives, design 1–2 experiments with hypothesis, method, metric and success threshold, then visualize the whole tree. Saves the result as markdown when it gets substantial.
One outcome at a time, opportunities before solutions, experiments with skin in the game. You need research data to feed it — interviews, surveys, analytics, feedback. Without that, the tree is guesswork.
What it helps with
- build an OST from an outcome and research data
- rank customer needs with Opportunity Score
- generate 3+ solutions per opportunity
- design an experiment with hypothesis, metric and success threshold
- output the full tree as markdown
Example prompts for the agent
- Build an opportunity solution tree for the outcome "increase 7-day retention to 40%" using these interview notes
- Here's survey data — map customer opportunities and prioritize them
- Generate solutions for the top three opportunities and suggest experiments
How to install opportunity-solution-tree
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a claude-code2Manually: put the files in place
~/.claude/skills/opportunity-solution-tree/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/opportunity-solution-tree/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a codex2Manually: put the files in place
.agents/skills/opportunity-solution-tree/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a cursor2Manually: put the files in place
.cursor/skills/opportunity-solution-tree/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install phuryn/pm-skills opportunity-solution-tree2Manually: put the files in place
.github/skills/opportunity-solution-tree/SKILL.md1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a gemini-cli2Platform CLI
gemini skills install https://github.com/phuryn/pm-skills --path pm-product-discovery/skills/opportunity-solution-treeManually: put the files in place
.devin/skills/opportunity-solution-tree/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about opportunity-solution-tree
How do I install opportunity-solution-tree in Claude Code?
Run npx skills add phuryn/pm-skills --skill opportunity-solution-tree -a claude-code. The skill lands in ~/.claude/skills/opportunity-solution-tree/SKILL.md.
What does opportunity-solution-tree do?
It builds an Opportunity Solution Tree that links a measurable outcome to customer opportunities, solutions, and experiments. The point is to map the opportunity space before jumping to features.
What input does the skill need?
A desired outcome or business metric, plus research data: interviews, surveys, analytics, feedback. Existing opportunities or solution ideas are optional.
Source text
SKILL.md · MIT
--- 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. ### 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 - [The Extended Opportunity Solution Tree](https://www.productcompass.pm/p/the-extended-opportunity-solution-tree) - [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery) - [Product Trio: Beyond the Obvious](https://www.productcompass.pm/p/product-trio) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
© phuryn · MIT · phuryn/pm-skills
Similar skills
All skills for Notes, tasks and projects →opportunity-solution-tree by other authors comes first.