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 VandanaAjayDubey111/great-pm --skill opportunity-solution-treegit clone --depth 1 https://github.com/VandanaAjayDubey111/great-pmWrote 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/vandanaajaydubey111/great-pm/opportunity-solution-tree)<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/opportunity-solution-tree"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/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/vandanaajaydubey111/great-pm/opportunity-solution-tree"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/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.00068 | $0.02421 |
| Opus 5.5 | $0.00027 | $0.00968 |
| Sonnet 5.5 | $0.00014 | $0.00484 |
| Haiku 4.5 | $0.00007 | $0.00242 |
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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex host binding
- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the
great-pm-runtimeskill and the selected packaged role file. - Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex
spawn_agentcall with that role and a bounded assignment. - For the spawn tool's
task_nameoragent_nameidentifier, replace canonical role-name hyphens with underscores (query-refiner-pm→query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename. - Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If
spawn_agentis unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set. - Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.
Provenance. Adapted from
phuryn/pm-skills@opportunity-solution-tree(MIT License, Paweł Huryn / Product Compass — github.com/phuryn/pm-skills). Framework is Teresa Torres, Continuous Discovery Habits. Vendored into great-pm 2026-05-29 with great-pm-convention frontmatter. MIT permits commercial use with attribution; this header is the attribution.
Opportunity Solution Tree (OST)
A visual framework for structuring continuous product discovery. Connects a desired outcome to customer opportunities, possible solutions, and experiments to validate them — preventing the team from jumping to solutions before mapping the opportunity space.
Structure — 4 levels
- Desired Outcome (top) — One measurable business/product outcome (e.g. "increase 7-day retention to 40%"). Comes from OKRs or strategy. Single metric.
- Opportunities (second) — Customer needs/pains/desires from research. These are problems worth solving, NOT features. Frame from the customer's view: "I struggle to…", "I wish I could…". Prioritize with Opportunity Score = Importance × (1 − Satisfaction) (Dan Olsen), Importance/Satisfaction on 0–1.
- Solutions (third) — Multiple ways to address each opportunity. Generate ≥3 per opportunity; don't commit to the first idea. Ideate as a Product Trio (PM + Designer + Engineer).
- Experiments (bottom) — Fast, cheap tests of whether a solution actually addresses the opportunity. Use assumption testing across Value, Usability, Viability, Feasibility. Prefer "skin-in-the-game" tests over opinions.
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 · 167 lines · 68 tokens per session scan A 16f3186655ea
opportunity-solution-tree is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 2,421 once invoked, about $0.0003 per session on Opus 5.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-09-21.
Other skills, from other repositories
werewolf-6p
Six-player Werewolf rules for a permanent Agent host, with the user choosing to join the randomized player pool or spectate.
avalon-8-10p
Eight-to-ten-player Avalon rules for a permanent Agent host, with the user choosing to join the randomized player pool or spectate.
execution-orchestrator
A planning and coordination skill for substantial coding tasks. It chooses how work should be organized, tracked, delegated, reviewed, and resumed across execution steps.
nexus-configuration
A skill for reading, planning, approving, and checking configuration in Nexus, the current private conversation or room. It covers settings such as agents, rooms, providers, channels, connectors, skills, models, tools, and MCP connections.
pptx
Instructions for reading, creating, and editing PowerPoint presentation files and templates, including .pptx, .potx, and older .ppt files. They cover text, tables, images, charts, layouts, and speaker notes.
wechat-article-search
A search workflow for finding WeChat public-account articles by keyword and organizing their titles, summaries, dates, account names, and links.