agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/opportunity-solution-tree/SKILL.md

opportunity-solution-tree

Skill114 starsChanged 10 months agoMITView on GitHub

Transform research into Opportunity Solution Tree (Teresa Torres method). Map outcomes, opportunities, solutions, and experiments.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prioritization-advisor, outcome-roadmap and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nandanosqlSkill

    prioritization-advisor

    Guide PMs in choosing the right prioritization framework — RICE, ICE, Kano, MoSCoW, Value vs Effort, Cost of Delay — by asking adaptive questions about product stage, team context, and data availability.

    Also in 5 projects that use this

  • skytiger6724Skill

    outcome-roadmap

    Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

    Also in 7 projects that use this

  • nandanosqlSkill

    business-health-diagnostic

    Run a comprehensive business health check across revenue, unit economics, product metrics, and market position — identifying strengths, weaknesses, and the single most important metric to fix.

    Also in 4 projects that use this

  • skytiger6724Skill

    brainstorm-experiments-new

    Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.

    Also in 7 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 6 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 8 projects that use this

  • +4 more from skytiger6724

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When synthesizing user research into a structured view of opportunities.

    line 12
  2. Distinctive:

    Create parent nodes where needed

    line 40
  3. Distinctive:

    Run distinctness checks across siblings

    line 41
  4. Distinctive:

    Run parent-child checks down branches

    line 42
  5. Distinctive:

    Remove generic parents with single children

    line 43
  6. Distinctive:

    All opportunities from user perspective

    line 79
  7. Distinctive:

    No solutions in the tree

    line 80
  8. Distinctive:

    Keep distinct across siblings

    line 81
  9. Distinctive:

    Prefer specific over generic

    line 82
  10. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 87

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Opportunity Solution Tree (OST)

Transform interview data into a structured Opportunity Solution Tree following Teresa Torres's method.

When to Use

When synthesizing user research into a structured view of opportunities.

Key Concepts

Opportunity: A customer need, pain, or desire - phrased from user perspective, not a solution.

Moment in time: A distinct point in the customer journey.

Tests:

  • Distinctness (siblings): Can we pursue one without addressing the other? If yes, they're distinct.
  • Parent-child: Does solving the child partially solve the parent? If not, reframe.

The Process

1. Extract Opportunities

From interviews, capture:

  • Verbatim quotes
  • Reframed user-need statement
  • Which journey moment it belongs to

2. Organize by Journey Moments

Group opportunities under their primary moment in time.

3. Structure Within Each Moment

  • Cluster similar opportunities
  • Create parent nodes where needed
  • Run distinctness checks across siblings
  • Run parent-child checks down branches
  • Remove generic parents with single children
  • Combine near-duplicates

4. Track Evidence

For each opportunity, capture:

  • Representative quotes
  • Frequency count
  • Confidence level (low/med/high)

5. Prioritize Leaves

Score leaf opportunities:

  • Impact (1-5)
  • Frequency (1-5)
  • Alignment to outcome (1-5)
  • Priority = Impact x Frequency x Alignment

Output Format

Opportunity Inventory Table: | ID | Moment | Opportunity | Parent ID | Quotes | Frequency | Confidence |

Tree View (per moment):

## [Moment Name]
- [Parent opportunity]
  - [Child opportunity]
    - [Grandchild]

Prioritized Leaf Backlog: Ranked list with scores and rationale.

Rules

  • All opportunities from user perspective
  • No solutions in the tree
  • Keep distinct across siblings
  • Prefer specific over generic
  • Preserve verbatim quotes for evidence

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free