
pm-opportunity-scoring
Score and rank product opportunities objectively with the Pragmatic Institute Opportunity Scoring model — across distinctive competency fit, competitive landscape, investment level, and impact to buyers/users. Use when the PM asks which idea to pursue, "score these opportunities", prioritize projects/bets, or compare options objectively instead of by opinion. Produces an Opportunity Scorecard as a Markdown or Word .docx artifact.
- Installs
- 41
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/julianoczkowski/product-manager --skill pm-opportunity-scoring- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pm-opportunity-scoring automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Opportunity Scoring (Pragmatic Framework: Focus / Business)
Evaluate candidate opportunities objectively so a decision rests on evidence, not the
loudest voice. Score each opportunity on four attributes using a 1-to-5 scale where
1 = Least Favorable and 5 = Most Favorable. See ../pm-copilot/references/framework.md.
The four attributes (1 = least favorable, 5 = most favorable)
| Attribute | What it measures | 1 (least) → 5 (most) |
|---|---|---|
| Distinctive Competencies | How much it relies on abilities we already have (valued, different, provable) | 1 = requires building a new competency → 5 = directly uses existing strong competencies |
| Competitive Landscape | Size/strength of alternatives | 1 = highly competitive (rival has pricing power/brand equity) → 5 = low competition (we can freeze out the market) |
| Investment Level | Resources (people, material, facilities) required | 1 = very high (ground-up build) → 5 = very low (re-use existing assets) |
| Impact to Buyers/Users | Consequences for current & potential customers | 1 = negative outweighs positive → 5 = significant positive impact / high ROI for buyer |
Total = sum of the four scores (4–20). Rank opportunities by total, but read the per-attribute scores too — a low Investment + high Impact "no brainer" may beat a higher total that depends on a competency you don't have.
Method
- List the candidate opportunities (ideally ones already validated as urgent, pervasive
and willing-to-pay — see
pm-market-problems). - Score each attribute 1–5 and write the rationale (the evidence) for each score.
- Sum, rank, and discuss — especially where scores are low on Distinctive Competencies (can we really win?) or Investment (can we afford it?).
Interview the user for inputs (batch questions)
- What are the opportunities to compare? (Name each + the market problem it solves.)
- For each: do we already have the competencies to deliver it, or must we build them?
- How competitive is the space (who else, how entrenched)?
- Rough investment — reuse existing assets, or ground-up?
- Expected impact/ROI for buyers and users (and any downside)?
Artifact template
# Opportunity Scorecard — <product/BU>
**Company:** <company> · **Feature / Product:** <feature / product name>
**Author:** <author> · **Date created:** <date> · **Version:** 1.0
**Scale:** 1 = Least Favorable → 5 = Most Favorable
| Opportunity | Distinctive Competencies | Competitive Landscape | Investment Level | Impact to Buyers/Users | Total | Rank |
| :--- | ---: | ---: | ---: | ---: | ---: | ---: |
| <Opportunity A> | 4 | 3 | 2 | 5 | 14 | 2 |
| <Opportunity B> | 5 | 4 | 4 | 4 | 17 | 1 |
## Rationale (evidence behind each score)
### <Opportunity A>
- **Distinctive Competencies (4):** <why>
- **Competitive Landscape (3):** <why>
- **Investment Level (2):** <why>
- **Impact to Buyers/Users (5):** <why>
## Recommendation
<Which opportunity(ies) to pursue and why — reference the scores and the market evidence.>
Deliver the artifact
Follow ../pm-copilot/references/artifact-output.md: confirm inputs, ask Markdown
or .docx, write the .md, convert via your environment's native document-creation capability on request. Next stage:
build the full business case for the winner with pm-product-canvas.
FAQ
What does the pm-opportunity-scoring skill do?
Score and rank product opportunities objectively with the Pragmatic Institute Opportunity Scoring model — across distinctive competency fit, competitive landscape, investment level, and impact to buyers/users. Use when the PM asks which idea to pursue, "score these opportunities", prioritize projects/bets, or compare options objectively instead of by opinion. Produces an Opportunity Scorecard as a Markdown or Word .docx artifact.
How do I install pm-opportunity-scoring?
Run npx skills add https://github.com/julianoczkowski/product-manager --skill pm-opportunity-scoring in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pm-opportunity-scoring/ (personal) or .claude/skills/pm-opportunity-scoring/ (project).
Which AI agents can use pm-opportunity-scoring?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pm-opportunity-scoring safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pm-opportunity-scoring?
It is published by julianoczkowski in julianoczkowski/product-manager. It has 41 recorded installs.
More from julianoczkowski/product-manager
pm-market-problems
julianoczkowski/product-manager
Run Pragmatic Institute market discovery and validate real market problems before anything gets built. Use when a PM says "I want to build a feature", "do market research", "talk to customers", "discovery", "validate this idea", "is this problem real", "NIHITO", or "who should I interview". Enforces the outside-in rule: build only for problems that are urgent, pervasive, and that the market will pay to solve. Produces a Market Discovery Document and a Market Problems Table as a Markdown or Word .docx artifact.
pm-copilot
julianoczkowski/product-manager
Open the skill to read its SKILL.md instructions.
pm-gap-analysis
julianoczkowski/product-manager
Open the skill to read its SKILL.md instructions.
pm-win-loss-analysis
julianoczkowski/product-manager
Open the skill to read its SKILL.md instructions.
pm-positioning
julianoczkowski/product-manager
Open the skill to read its SKILL.md instructions.
pm-product-strategy
julianoczkowski/product-manager
Open the skill to read its SKILL.md instructions.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.