opportunity-solution-tree

Transform stakeholder requests into measurable outcomes, opportunities, and tested solutions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill opportunity-solution-tree-locus-taxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-solution-tree
Source: https://github.com/locus-taxy/locus-SD-toolkit/tree/main/skills/opportunity-solution-tree
Command: npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill opportunity-solution-tree-locus-taxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OST skill helps product teams transform vague stakeholder requests into structured discovery by identifying desired outcomes, exploring customer problems (opportunities), mapping potential solutions, and selecting a validated POC based on feasibility, impact, and market fit. It promotes divergence before convergence and ensures experiments are linked to each solution.

Core Features & Use Cases

  • Outcome-driven discovery: start from a measurable outcome and align opportunities accordingly.
  • Multi-phase workflow: Phase 1 OST generation, Phase 2 POC selection, with scoring and experiment definition.
  • Output artifacts: Opportunity Solution Tree + POC plan, ready for execution and learning.

Quick Start

Provide a stakeholder request and follow the prompts to produce an OST with opportunities, solutions, and a POC plan.

Frequently Asked Questions about opportunity-solution-tree

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

FAQPage Schema
What is an opportunity solution tree and how does it frame product discovery?

An opportunity solution tree structures product discovery by mapping a desired outcome to customer opportunities, testing solutions, and defining experiments. It aligns stakeholder requests with measurable product-management goals.

How do I turn stakeholder requests into measurable outcomes and tested solutions?

Transform stakeholder requests into measurable outcomes by guiding discovery through two phases: generating an opportunity solution tree and selecting a proof-of-concept. This maps outcomes to validated solutions and experiments.

How can I map product experiments to specific solutions during discovery?

Map product experiments to solutions by structuring discovery through an opportunity solution tree. This ensures every proposed solution is directly linked to an underlying customer opportunity and a validating experiment.

What is the best way to select a proof-of-concept for product management?

Select a proof-of-concept by evaluating potential solutions against feasibility, impact, and market fit. This structured scoring approach ensures the chosen POC aligns with desired outcomes and validated opportunities.

Can I use this discovery approach for any stakeholder request?

Yes, you can use this discovery approach for any stakeholder request. It promotes divergence before convergence, transforming vague requests into structured outcomes, opportunities, and a tested POC plan.

When should I not use an opportunity solution tree for product discovery?

Avoid using an opportunity solution tree when stakeholder requests lack a clear desired outcome. The framework requires aligning opportunities to measurable goals to successfully select a proof-of-concept.