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.
npx agentmods add skills/getcrew44/crew44/opportunity-solution-treenpx skills add getcrew44/crew44 --skill opportunity-solution-treegit clone --depth 1 https://github.com/getcrew44/crew44Wrote 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.
[](https://agentmods.dev/skills/getcrew44/crew44/opportunity-solution-tree)<a href="https://agentmods.dev/skills/getcrew44/crew44/opportunity-solution-tree"><img src="https://agentmods.dev/badge/skills/getcrew44/crew44/opportunity-solution-tree.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00036 | $0.03785 |
| Opus 5 | $0.00018 | $0.01893 |
| Sonnet 5 | $0.00007 | $0.00757 |
| Haiku 4.5 | $0.00004 | $0.00379 |
Grade A, and why
opportunity-solution-tree 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- opportunity-solution-tree — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Guide product managers through creating an Opportunity Solution Tree (OST) by extracting target outcomes from stakeholder requests, generating opportunity options (problems to solve), mapping potential solutions, and selecting the best proof-of-concept (POC) based on feasibility, impact, and market fit. Use this to move from vague product requests to structured discovery, ensuring teams solve the right problems before jumping to solutions—avoiding "feature factory" syndrome and premature convergence on ideas.
This is not a roadmap generator—it's a structured discovery process that outputs validated opportunities with testable solution hypotheses.
Key Concepts
What is an Opportunity Solution Tree (OST)?
An OST is a visual framework (Teresa Torres, Continuous Discovery Habits) that connects:
- Desired Outcome (business goal or product metric)
- Opportunities (customer problems, needs, pain points, or desires that could drive the outcome)
- Solutions (ways to address each opportunity)
- Experiments (tests to validate solutions)
Structure:
Desired Outcome (1)
|
+-----------+-----------+
| | |
Opportunity Opportunity Opportunity (3)
| | |
+-+-+ +-+-+ +-+-+
| | | | | | | | |
S1 S2 S3 S1 S2 S3 S1 S2 S3 (9 total solutions)
Why This Works
- Outcome-driven: Starts with business goal, not feature requests
- Divergent before convergent: Explores multiple opportunities before picking solutions
- Problem-focused: Opportunities are problems, not solutions disguised as problems
- Testable: Each solution maps to experiments, not just "build it and ship"
- POC selection: Evaluates feasibility, impact, market fit before committing resources
Anti-Patterns (What This Is NOT)
- Not a feature list: Opportunities are problems customers face, not "we need dark mode"
- Not solution-first: Don't start with "we should build X"—start with "customers struggle with Y"
- Not waterfall planning: OST is a discovery tool, not a project plan
- Not a one-time exercise: OSTs evolve as you learn from experiments
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 421 lines · 36 tokens per session scan A 87a5d8a25af6
opportunity-solution-tree is a skill published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 3,785 once invoked, about $0.0002 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.
Other skills, from other repositories
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…
zcode-delegate
Delegate a coding task to the Z.AI ZCode CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to ZCode — phrasings like "have ZCode do X", "delegate this to ZCode", "run it through ZCode", or "use ZCode to implement/fix/refactor" — or…