opportunity-tree
Skill25 starsChanged 9 days agoMITView on GitHub
Teresa Torres OST (Opportunity Solution Tree) + gstack Six Forcing Questions 자가검증. outcome → opportunity → solution → experiment 매핑. PM 자체 reasoning, 사용자 Q&A 안 함.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Pearl1531/Archetype-talktheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Pearl1531/Archetype-talk★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- build-testSkill
- trend-trackerSkill
- typecheckSkill
- agent-managerSkill
- cron-managerSkill
- design-systemSkill
- discovery-synthesisSkill
- docsSkill
- experiment-designSkill
- goal-managerSkill
- hypothesis-designSkill
- interview-scriptSkill
- jobs-storiesSkill
- lean-canvasSkill
- market-researchSkill
- meceSkill
- okrSkill
- policySkill
- prdSkill
- premortemSkill
- primitive-reviewSkill
- prioritizationSkill
- retrospectiveSkill
- skill-managerSkill
- skill-refinementSkill
- triageSkill
- wbsSkill
- workflow-managerSkill
- workflow-refinementSkill
- xyz-hypothesisSkill
The file
Files
Opportunity Tree Skill
Teresa Torres CDH (Continuous Discovery Habits) 의 OST 자체 실행. Outcome 에서 시작해 opportunity, solution, experiment 까지 트리 형태로 분해.
구조
Outcome (team OKR 의 KR)
└─ Opportunity 1 (사용자 unmet need)
├─ Solution 1.1
│ └─ Experiment 1.1.a
└─ Solution 1.2
└─ Experiment 1.2.a
└─ Opportunity 2
├─ Solution 2.1
└─ Solution 2.2입력
- team OKR (Layer 4a)
discovery-synthesis출력 (JTBD signals)
Six Forcing Questions (gstack 차용) — 자가검증 체크리스트
각 opportunity / solution 에 대해 PM 이 스스로 답해본다. 답할 수 없으면 → open_questions[]:
- Demand Reality: "사용자가 진짜 원하는가, 흥미만 표현하나?"
- Interest is not demand.
- Status Quo: "현재 사용자가 이미 어떻게 해결하나?"
- Status quo is your real competitor.
- Desperate Specificity: "Y segment 가 X 를 지금 절박하게 원하나?"
- Narrowest Wedge: "가장 좁고 깊은 진입점은?"
- Observation & Surprise: "예상 못한 패턴 발견했나?"
- Future-Fit: "이 솔루션이 6개월 뒤에도 유효한가?"
출력
{
"outcome": "OKR KR 인용",
"tree": [
{
"opportunity": "...",
"jtbd_ref": "...",
"six_questions": {
"demand_reality": "...",
"status_quo": "...",
"desperate_specificity": "...",
"narrowest_wedge": "...",
"observation": "...",
"future_fit": "..."
},
"solutions": [
{
"title": "...",
"approach": "...",
"experiments": [
{ "spec": "...", "metric": "...", "expected": "..." }
]
}
]
}
],
"open_questions": [...]
}HARD GATE
- Six Forcing Questions 6 항목 모두 자가응답 또는 open_question
- Opportunity 당 Solution ≥2 (gstack rule)
- Solution 당 Experiment ≥1
Anti-Sycophancy
- ❌ "이 opportunity 가 흥미롭습니다"
- ✅ "이 opportunity 는 demand 신호 N건, status quo 분석 Y. Z 가 사실로 드러나면 우선순위 낮춤."
Reference
- Teresa Torres "Continuous Discovery Habits"
- gstack
/office-hoursSix Forcing Questions - phuryn/pm-skills/pm-product-discovery/opportunity-solution-tree
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
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.

