SKILL FILE

Opportunity Solution Tree with AI

Build Teresa Torres-style Opportunity Solution Trees mapping business outcomes → user opportunities → testable solutions. Continuous discovery as a doc.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Outcome-rooted tree

Every tree starts with a clear business or product outcome — not a feature wish-list.

2

Opportunity branches

Each opportunity is a user need framed as a problem statement, not a solution.

3

Solution leaves

Each opportunity gets 2–4 candidate solutions, kept lightweight so you can compare without committing.

4

Experiment nodes

Each solution attaches to one or more experiments that would prove or disprove it.

5

Tree visualisation

Output is a clean nested structure (Markdown or Miro-ready) you can share with stakeholders.

What you can build with this

Start a new product initiative

Before locking a solution, map the opportunity space so you don't miss higher-leverage paths.

Quarterly planning

Use the tree to align user needs with business goals before committing to a roadmap.

Stakeholder alignment

A shared tree gives execs, design, and engineering the same picture of WHY.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

Teresa Torres is a product discovery coach whose book "Continuous Discovery Habits" popularised Opportunity Solution Trees. The framework keeps discovery and delivery connected by making the chain from outcome to experiment explicit.
A roadmap shows what you'll build and when. An OST shows why you're considering each option and how you'll test it. They're complementary — the tree feeds the roadmap.
You can sketch a starting tree from internal hypotheses, but the opportunities should be grounded in research before you commit to building. The skill works best with research as input.
Usually 4–8 distinct opportunities. Fewer and you've probably narrowed too early; more and you haven't found the right level of abstraction.
No — trees are working documents, not encyclopaedias. Capture the opportunities you're actively considering, add more as you discover them.

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →