opportunity-solution-tree

Structure stakeholder requests into an Opportunity Solution Tree with outcomes, opportunities, and POC experiments.

358|11|Updated May 15, 2026
One-click install
npx skills add https://github.com/getcrew44/crew44 --skill opportunity-solution-tree-getcrew44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-solution-tree
Source: https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/product/opportunity-solution-tree
Command: npx skills add https://github.com/getcrew44/crew44 --skill opportunity-solution-tree-getcrew44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams move from ambiguous stakeholder requests to a structured Opportunity Solution Tree that clarifies outcomes, surfaces the real problems to solve, and maps solutions to experiments instead of jumping straight to building features.

Core Features & Use Cases

  • Outcome extraction and framing: Identifies measurable target outcomes from stakeholder input (what metric you’re trying to move).
  • Opportunity generation: Produces multiple customer/problem-driven opportunities (what needs to be true for the outcome to happen).
  • Solution mapping and POC selection: Generates solution options for a chosen opportunity and recommends a best proof-of-concept using feasibility, impact, and market fit, including an experiment plan to validate assumptions.
  • Use cases: Kickoff for new product initiatives, clarifying OKRs, aligning stakeholders during discovery, and avoiding “feature factory” syndrome.

Quick Start

Use the skill by pasting the stakeholder request and asking the agent to create an Opportunity Solution Tree and recommend the best first POC with an experiment plan.

Frequently Asked Questions about opportunity-solution-tree

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

FAQPage Schema
How do I turn vague stakeholder requests into testable product bets?

To turn vague stakeholder requests into testable product bets, structure the input into an Opportunity Solution Tree by extracting measurable desired outcomes, generating multiple opportunity options, and mapping each to testable solution and experiment hypotheses.

What is continuous discovery and how does problem framing avoid solution-first feature planning?

Continuous discovery uses problem framing to identify real customer needs before development. By focusing on opportunity generation and measurable outcomes rather than features, teams avoid solution-first planning and ensure they build products that address actual user problems.

How do I align stakeholders during product discovery workshops?

Align stakeholders during product discovery workshops by collaboratively building an Opportunity Solution Tree. This interactive facilitation extracts target outcomes, generates three opportunities, maps solutions, and scores options on feasibility, impact, and market fit to recommend a POC experiment.

How do I select the best POC experiment for a new product initiative?

Select the best POC experiment for a product initiative by scoring your solution options on feasibility, impact, and market fit. After mapping these solutions to specific opportunities within your tree, the highest-scoring option becomes your recommended proof-of-concept validation plan.

When should I use an Opportunity Solution Tree instead of jumping straight to building features?

Use an Opportunity Solution Tree instead of jumping straight to building features when you need early-stage discovery, OKR clarification, or stakeholder alignment. It prevents the feature factory syndrome by ensuring teams validate assumptions and frame problems before development.