opportunity-solution-tree

Guide product managers through creating an Opportunity Solution Tree.

24|3|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill opportunity-solution-tree-prorise-cool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-solution-tree
Source: https://github.com/Prorise-cool/prorise-claude-skills/tree/main/.claude/skills/product-specialist/references/domains/product-management/opportunity-solution-tree
Command: npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill opportunity-solution-tree-prorise-cool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps product managers move from vague stakeholder requests to validated product opportunities by structuring the discovery process, ensuring teams solve the right problems before building solutions.

Core Features & Use Cases

  • Outcome-Driven Discovery: Starts with a clear business goal and works backward to identify customer problems (opportunities) and potential solutions.
  • Structured Problem Framing: Guides users through defining opportunities, mapping solutions, and selecting the best Proof-of-Concept (POC) for validation.
  • Use Case: A stakeholder requests a new feature. Use this Skill to define the desired outcome (e.g., increase conversion rate), identify the underlying customer problems that prevent this outcome, brainstorm solutions for those problems, and plan an experiment to test the most promising solution.

Quick Start

Guide me through creating an Opportunity Solution Tree for a new feature request.

Frequently Asked Questions about opportunity-solution-tree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure product discovery to connect desired outcomes with customer problems?

Product discovery can be structured using an Opportunity Solution Tree to map desired business outcomes to underlying customer problems, potential solutions, and validation experiments. This ensures teams solve the right problems before building features.

What is the best way to validate solutions for a new product feature request?

The best way to validate solutions is by selecting a Proof-of-Concept (POC) based on feasibility, impact, and market fit. You can structure this validation by planning experiments to test the most promising solutions mapped to specific customer problems.

How do I frame vague stakeholder feature requests as clear product opportunities?

Vague stakeholder requests are framed as product opportunities by defining the desired business outcome, identifying the underlying customer problems preventing that outcome, and brainstorming targeted solutions. This structured problem framing moves teams from requests to validated opportunities.

Can I use this product discovery process for optimizing conversion rate improvements?

Yes, you can use this product discovery process for goals like increasing conversion rates. It guides you to identify the specific customer problems preventing the desired outcome, brainstorm solutions, and run validation experiments to test the most promising approaches.

How do I identify which proof-of-concept to select for solution validation?

You select a proof-of-concept for solution validation by evaluating potential solutions based on their feasibility, impact, and market fit. This evaluation happens after mapping the desired outcomes and identifying the underlying customer problems.