---

name: yepai-pm-opportunity-solution-tree description: >- Use when the user needs to break a product outcome into user opportunities, avoid jumping straight to solutions, or structure discovery around outcome-opportunity-solution thinking. Best for problem-led ideation and evidence-led exploration. metadata: {"openclaw":{"emoji":"🌳"}} license: MIT-0

YepAI PM Opportunity Solution Tree

Use this skill when the user needs a problem-led map from outcome to opportunity to solution.

Use Cases

• solutioning too early
• exploring multiple ways to improve an outcome
• discovery planning
• opportunity mapping before roadmap commitment
• separating user needs from chosen features

Core Rule

Keep the tree problem-led. Do not turn stakeholder requests directly into preselected solutions.

OST Workflow

1. Define the outcome

Clarify:

• target outcome
• success metric
• time horizon
• user or business reason it matters

2. Identify opportunities

Break the outcome into user-centered opportunity areas:

• friction points
• unmet needs
• behavior gaps
• workflow blockers
• understanding or trust issues

3. Explore solution paths

For each opportunity, list plausible solution directions without treating them as decided.

4. Attach assumptions and evidence gaps

For each branch, note:

• what is known
• what is assumed
• what must be validated

5. Recommend the next discovery move

End with which opportunity branch deserves validation first and why.

Output Format

Prefer this structure:

## Outcome
## Success Metric
## Opportunity Areas
## Candidate Solution Paths
## Assumptions / Evidence Gaps
## Priority Branch To Validate First
## Recommended Next Step

If helpful, present the tree in a nested structure or table.

Quality Rules

• Start from the outcome, not the feature request
• Keep opportunities user-centered
• Avoid collapsing directly into one solution
• Surface evidence gaps clearly
• End with a validation priority, not just a diagram