Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Install Define Opportunity Tree
$ npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills define-opportunity-tree --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/define-opportunity-tree .claude/skills/define-opportunity-tree && rm -rf skills-srcUse ~/.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/
Install the "define-opportunity-tree" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-tree into .claude/skills/define-opportunity-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "define-opportunity-tree", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-treeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills define-opportunity-tree --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/define-opportunity-tree .agents/skills/define-opportunity-tree && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "define-opportunity-tree" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-tree into .agents/skills/define-opportunity-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "define-opportunity-tree", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills define-opportunity-tree --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/define-opportunity-tree .cursor/skills/define-opportunity-tree && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "define-opportunity-tree" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-tree into .cursor/skills/define-opportunity-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "define-opportunity-tree", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/define-opportunity-tree--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills define-opportunity-tree --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/define-opportunity-tree .gemini/skills/define-opportunity-tree && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "define-opportunity-tree" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-tree into .gemini/skills/define-opportunity-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "define-opportunity-tree", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills define-opportunity-treeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/define-opportunity-tree .github/skills/define-opportunity-tree && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "define-opportunity-tree" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-tree into .github/skills/define-opportunity-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "define-opportunity-tree", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills define-opportunity-tree --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/define-opportunity-tree .opencode/skills/define-opportunity-tree && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "define-opportunity-tree" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-opportunity-tree into .opencode/skills/define-opportunity-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "define-opportunity-tree", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
define-opportunity-tree- GitHub stars
- 716
- Token cost
- ~1.1k tokens
- SKILL.md length
- 497 words
- Files
- 5 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
- Works in 7 steps: Define the Desired Outcome → Identify Opportunity Areas → Add Supporting Evidence → …
- Structuring scattered feature ideas
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Format, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Define Opportunity Tree is an agent skill from product-on-purpose/pm-skills. Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).
It sits in Product & Project Management, covering Prioritization frameworks. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Structuring scattered feature ideas
- Communicating how the roadmap traces to outcomes
Example prompts
- “Use the define-opportunity-tree skill to create an opportunity solution tree connecting a desired outcome to customer opportunities and candidate…”
- “/define-opportunity-tree”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Define the Desired Outcome
- Identify Opportunity Areas
- Add Supporting Evidence
- Brainstorm Solutions
- Define Assumption Tests
- Prioritize the Tree
- Visualize the Structure
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. 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
No URLs in SKILL.md.
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
Define Opportunity Tree loads about 1.1k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 497 words of instructions outside code blocks.
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 product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 497 words, ~1,107 tokens.
Download SKILL.mdSave it as
.claude/skills/define-opportunity-tree/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- define-opportunity-tree
- description
- Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.
- license
- Apache-2.0
- metadata.phase
- define
- metadata.version
- 2.2.0
- metadata.updated
- 2026-07-04
- metadata.category
- problem-framing
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->Opportunity Solution Tree
An Opportunity Solution Tree (OST) is a visual framework for product discovery that connects business outcomes to customer opportunities and potential solutions. Developed by Teresa Torres, it prevents the common trap of jumping straight to solutions by ensuring every feature idea traces back to a customer need and measurable outcome.
When to Use
- During continuous product discovery to organize learning
- When prioritizing what opportunities to pursue
- To communicate product strategy to stakeholders
- When you have too many feature ideas and need structure
- After user research to connect insights to action
- When aligning team on what outcomes matter most
When NOT to Use
- You need to score and rank a flat list of known candidates -> use
define-prioritization-framework; the tree structures discovery, not a ranking exercise - You have one specific problem to frame for a team -> use
define-problem-statement - You are ready to test a single assumption -> use
define-hypothesis, thenmeasure-experiment-design - The outcome you want to drive is not yet agreed -> set it first with
foundation-okr-writer; a tree without an agreed outcome decorates opinions
Instructions
When asked to create an opportunity solution tree, follow these steps:
Define the Desired Outcome Start at the top with a clear, measurable business or product outcome. This should be something you can influence through product changes. Express it quantitatively when possible (e.g., "Increase 30-day retention from 40% to 55%").
Identify Opportunity Areas Branch out to 3-5 opportunity areas.places where customer needs or pain points could be addressed. Opportunities are not solutions; they're customer problems, needs, or desires. Phrase them from the customer's perspective.
Add Supporting Evidence For each opportunity, note the evidence that supports it: user research quotes, behavioral data, support tickets, or market trends. Strong opportunities have multiple evidence sources.
Brainstorm Solutions For each opportunity, generate 2-4 potential solutions. Don't self-censor at this stage. Solutions can range from quick experiments to major features. Keep them specific enough to evaluate.
Define Assumption Tests For each promising solution, identify the riskiest assumption and design a lightweight experiment to test it. Good tests validate whether the solution will actually address the opportunity.
Prioritize the Tree Not all branches are equal. Mark which opportunity and solution you'll pursue first based on potential impact, confidence, and effort. The tree is a living document.you'll iterate as you learn.
Visualize the Structure Create a tree diagram showing the hierarchy: outcome at top, opportunities below, solutions beneath each opportunity, and experiments at the leaves.
Show full SKILL.md (87 more words)Show less
Output Format
Use the template in references/TEMPLATE.md to structure the output. A complete tree fills every template section: Desired Outcome; Visual Tree; Opportunity Branches; Prioritization; Experiments Backlog; Learning Log; and Next Steps.
Quality Checklist
Before finalizing, verify:
- Outcome is measurable and within product team's influence
- Opportunities are customer-centric (needs/problems, not features)
- Each opportunity has supporting evidence documented
- Multiple solutions exist per opportunity (not jumping to one)
- Assumptions are explicit and experiments designed
- Prioritization is clear (which branch to explore first)
Examples
See references/EXAMPLE.md for a completed example.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/define-opportunity-tree of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Define Opportunity 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Define Opportunity Tree this skillproduct-on-purpose/pm-skills | 716 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Prioritization Framework Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.2k | Automated safety check: Pass | Custom licence | |
| Strategic Roadmap Planningdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.7k | Automated safety check: Pass | Custom licence | |
| Idea Validatoraakashg/pm-claude-skills | 112 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Triagejoa23/linear-cli | 144 | — | ~699 | Automated safety check: Pass | MIT |
Similar skills
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
Idea Validator
aakashg/pm-claude-skills
A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.
Triage
joa23/linear-cli
Triage and prioritize Linear backlog issues using the linear CLI.
Topissues
fullsend-ai/fullsend
Build a merged RICE priority table: top unassigned backlog issues plus issues assigned to the current user.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Deliver Prd
product-on-purpose/pm-skills
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured.
Related
Categories
Questions about Define Opportunity Tree
What does Define Opportunity Tree do?
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Define Opportunity Tree is an agent skill from product-on-purpose/pm-skills. Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
When should I use Define Opportunity Tree?
Define Opportunity Tree fits situations like: structuring scattered feature ideas; communicating how the roadmap traces to outcomes.
How do I install Define Opportunity Tree in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a claude-code`. Or copy the skill folder (skills/define-opportunity-tree in product-on-purpose/pm-skills) into .claude/skills/define-opportunity-tree in your project. Claude Code loads it when a task matches its description.
How do I install Define Opportunity Tree in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill define-opportunity-tree -a codex`. Or copy the skill folder (skills/define-opportunity-tree in product-on-purpose/pm-skills) into .agents/skills/define-opportunity-tree in your project. Codex loads it when a task matches its description.
Can I use Define Opportunity 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 product-on-purpose/pm-skills --skill define-opportunity-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/define-opportunity-tree, .gemini/skills/define-opportunity-tree, .github/skills/define-opportunity-tree and .opencode/skills/define-opportunity-tree in your project.
What does Define Opportunity Tree need to run?
SKILL.md names no scripts, command-line tools or credentials: Define Opportunity Tree is instructions for the agent only.
Does Define Opportunity Tree access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Define Opportunity 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 Define Opportunity Tree use?
Define Opportunity Tree is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Define Opportunity Tree use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Define Opportunity Tree?
Skills that share tags, products or a category with Define Opportunity Tree: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Prioritization Framework Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars) and Idea Validator (aakashg/pm-claude-skills, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Define Opportunity Tree?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/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.