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 skills add derricktang/pm-workflow-plugin --skill opportunity-solution-treegit clone --depth 1 https://github.com/derricktang/pm-workflow-pluginWrote 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/derricktang/pm-workflow-plugin/opportunity-solution-tree)<a href="https://agentmods.dev/skills/derricktang/pm-workflow-plugin/opportunity-solution-tree"><img src="https://agentmods.dev/badge/skills/derricktang/pm-workflow-plugin/opportunity-solution-tree/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.
<a href="https://agentmods.dev/skills/derricktang/pm-workflow-plugin/opportunity-solution-tree"><img src="https://agentmods.dev/badge/skills/derricktang/pm-workflow-plugin/opportunity-solution-tree.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.03863 |
| Opus 5.5 | $0.00014 | $0.01545 |
| Sonnet 5.5 | $0.00007 | $0.00773 |
| Haiku 4.5 | $0.00004 | $0.00386 |
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 1mo 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.
This is a copy
100% identical to opportunity-solution-tree — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 427 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.
- 1mo ago First seen · 427 lines · 36 tokens per session scan A 90cd1bf80484
opportunity-solution-tree is a skill published in the GitHub repository derricktang/pm-workflow-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 3,863 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to opportunity-solution-tree, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-design
A workflow guide for turning an existing software change into a detailed technical design document. It builds on earlier proposal and design files and defines implementation risks, tests, and edge cases.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.