Individual skill
product-opportunity-tree
Map a measurable product outcome to customer opportunities, solution options, and assumption tests. Use for: opportunity solution tree, product discovery map, customer opportunity mapping, outcome-to-solution planning.
.grok/skills/product-opportunity-tree/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,388 bytes
Read excerpt
# Product Opportunity Tree
## Purpose
Create an evidence-aware opportunity tree that connects a desired outcome to customer needs, candidate solutions, and assumption tests. Use it to avoid treating a feature idea as the problem definition.
## Workflow
1. Define one measurable outcome that the team can influence, including its current baseline if known.
2. List customer opportunities as needs, barriers, or desired outcomes rather than proposed features.
3. Attach evidence to each opportunity and label it as observed, reported, inferred, or unknown.
4. Generate multiple solution options for promising opportunities; do not select a solution merely because it was proposed first.
5. Identify the riskiest assumption for each selected solution and define the smallest ethical test that could reduce uncertainty.
6. Prioritize the next branch using impact, confidence, effort, and evidence quality.