opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.
80
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-product-discovery/skills/opportunity-solution-tree/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates what the skill does (builds Opportunity Solution Trees for product discovery), when to use it (structuring discovery, mapping opportunities, deciding what to build), and grounds it in a specific methodology (Teresa Torres' Continuous Discovery Habits). It uses third person voice, includes natural trigger terms, and occupies a distinct niche that minimizes conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build an Opportunity Solution Tree', 'map a desired outcome to opportunities, solutions, and experiments', and 'structuring discovery work'. It also names the specific framework (Teresa Torres' Continuous Discovery Habits). | 3 / 3 |
Completeness | Clearly answers both 'what' (build an OST to map outcomes to opportunities, solutions, and experiments) and 'when' (explicit 'Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Opportunity Solution Tree', 'OST', 'product discovery', 'opportunities', 'solutions', 'experiments', 'deciding what to build next', 'Continuous Discovery Habits', 'Teresa Torres'. These cover both the framework name and the general problem space. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the Opportunity Solution Tree is a specific, well-defined framework with a clear niche. The mention of Teresa Torres and the specific terminology (OST, opportunities, solutions, experiments) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for building an Opportunity Solution Tree but suffers from being too explanatory and not concrete enough. The domain context section over-explains concepts that could be condensed, while the actual process steps lack the specificity (examples, templates, output formats) that would make them truly actionable. Adding a concrete example of a completed mini-OST and tightening the domain context would significantly improve it.
Suggestions
Add a concrete example of a completed OST (even a small one) showing the exact output format expected — e.g., a markdown tree for 'increase 7-day retention' with 2-3 opportunities, solutions, and experiments filled in.
Condense the Domain Context section by removing explanations Claude already knows (what a Product Trio is, who Teresa Torres is) and keeping only the operational details like the Opportunity Score formula and the 4-level structure.
Add a validation checkpoint after step 2 or 3 — e.g., 'Verify each opportunity is framed from the customer perspective and is a need/pain, not a feature request. Reframe any that sound like solutions.'
Include a concrete experiment example template: 'Hypothesis: [If we X, then Y]. Method: [prototype/survey/fake door]. Metric: [click-through rate]. Threshold: [>15% indicates signal].' to make step 5 actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content that Claude would already know (e.g., explaining what an OST is, attributing quotes, explaining the Product Trio concept). The domain context section is fairly verbose and could be tightened, though it does contain some useful specifics like the Opportunity Score formula. | 2 / 3 |
Actionability | The process steps provide a reasonable framework but remain at a fairly abstract level — there are no concrete examples of a completed OST, no template showing exact output format, and no executable artifacts. The experiment design step mentions 'hypothesis, method, metric, success threshold' but doesn't show a concrete example of what one looks like. | 2 / 3 |
Workflow Clarity | The 6-step process is clearly sequenced and logical, but lacks validation checkpoints or feedback loops. Step 6 says 'visualize the tree' but there's no verification step to check if the tree is well-formed, balanced, or if opportunities are properly scoped. The note about 'discovery is not linear' in principles hints at iteration but isn't operationalized in the workflow. | 2 / 3 |
Progressive Disclosure | The Further Reading section provides external references, but the skill itself is somewhat monolithic — the lengthy Domain Context section could be separated or condensed. The external links are all to the same blog/course rather than local reference files. The structure has clear sections but the domain context and instructions blend together without clear navigation signals. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- phuryn/pm-skills
- Commit
36ccefd
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.