opportunity-solution-trees

opportunity-solution-trees is a skill for Claude Code, Codex from wdavidturner/product-skills. It costs 68 tokens per session (1,072 once invoked), scanned A, original, MIT.

A tree-shaped product-planning framework that links a business goal to customer needs, possible solutions, and tests. An opportunity means an unmet customer need, not a feature idea.

In plain words
What is it for?
Use it to structure customer discovery, compare solutions for one need, and connect product decisions to business results. It also creates a shared view for product teams and stakeholders.
Why use it?
It stops teams from jumping straight to a preferred feature before understanding the customer problem. It keeps research, priorities, and delivery connected to a measurable outcome.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to structure customer discovery, compare solutions for one need, and connect product decisions to business results. It also creates a shared view for product teams and stakeholders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wdavidturner/product-skills/opportunity-solution-trees
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wdavidturner/product-skills --skill opportunity-solution-trees
Clone the repo
git clone --depth 1 https://github.com/wdavidturner/product-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for opportunity-solution-trees

README.md
[![agentmods](https://agentmods.dev/badge/skills/wdavidturner/product-skills/opportunity-solution-trees/github.svg)](https://agentmods.dev/skills/wdavidturner/product-skills/opportunity-solution-trees)
Your own site
<a href="https://agentmods.dev/skills/wdavidturner/product-skills/opportunity-solution-trees"><img src="https://agentmods.dev/badge/skills/wdavidturner/product-skills/opportunity-solution-trees/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for opportunity-solution-trees

Your own site · 80×15
<a href="https://agentmods.dev/skills/wdavidturner/product-skills/opportunity-solution-trees"><img src="https://agentmods.dev/badge/skills/wdavidturner/product-skills/opportunity-solution-trees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,072 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.01072
Opus 5 $0.00034 $0.00536
Sonnet 5 $0.00014 $0.00214
Haiku 4.5 $0.00007 $0.00107

Measured 12d ago against content hash cb4f6b6c4dc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

opportunity-solution-trees scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/opportunity-solution-trees/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Opportunity Solution Trees

What It Is

Use the Opportunity Solution Tree (OST) to connect a business outcome to the customer opportunities that drive it, then compare solutions and tests. The tree forces you to separate needs from ideas and keeps discovery tied to delivery.

When to Use It

  • Structure discovery around customer opportunities
  • Tie customer needs to measurable outcomes
  • Compare multiple solutions for the same opportunity
  • Keep continuous discovery aligned with the roadmap
  • Create a shared view of priorities with stakeholders

When Not to Use It

  • You are not doing customer research
  • The solution is already decided
  • The work is a commodity requirement with no real options
  • You only need a quick one-off decision

Patterns

Detailed examples showing how to apply OST correctly. Each pattern shows a common mistake and the correct approach.

Critical (get these wrong and you've wasted your time)

Pattern What It Teaches
opportunities-are-solutions "Add a search bar" is a solution -- the opportunity is what's hard about finding things
starting-with-solutions Work backward from outcomes, not forward from feature ideas
skipping-outcome Without a clear outcome, you can't evaluate which opportunities matter most
interviewing-for-facts Collect stories, not preferences -- needs emerge from what happened
conference-room-opportunities You can't hypothesize opportunities without customer research

High Impact

Pattern What It Teaches
single-solution-thinking Always compare at least 3 solutions for any opportunity
opportunities-too-big "Make it easier to use" is not actionable -- decompose into specific moments
flat-tree-structure Opportunities should nest hierarchically from broad to specific
missing-experience-map Structure opportunities around the customer journey, not internal categories
output-not-outcome "Launch feature X" is an output -- "Increase activation by 10%" is an outcome
solution-testing-whole-idea Break solutions into assumptions and test the riskiest ones first

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 103 lines · 68 tokens per session scan A cb4f6b6c4dc8

Subscribe to this mod's changes

opportunity-solution-trees is a skill published in the GitHub repository wdavidturner/product-skills (20 stars, last pushed 7mo ago), licensed MIT. It adds 68 tokens to every session and 1,072 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens