Skip to content
Back to skills

Product

ASecurity

Assess a product opportunity with Wardley mapping, market sizing, a North-Star metric, and RICE-ranked bets.

  • 23 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 14, 2026
ai-agentsrustgorailsawssecurity

Works with

  • cli

Security analysis

A100/100

Pro scans all 21 files and shows the line behind each finding

Scanned October 14, 2026

npx -y skills add andreibesleaga/GABBE --skill product --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Product?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Product
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreibesleaga-product-902c171c/badge)](https://www.skillsdirectory.com/skills/andreibesleaga-product-902c171c)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: opportunity-assessment
description: Assess a product opportunity with Wardley mapping, market sizing, a North-Star metric, and RICE-ranked bets.
triggers: [assess product opportunity, wardley map value chain, size market tam sam som, define north star metric, apply heart framework, rice prioritization of bets, write opportunity brief]
tags: [product, strategy, prioritization]
core: false
context_cost: medium
---
# Opportunity Assessment

## Goal
Evaluate whether a product opportunity is worth pursuing and which specific bets to make first. The skill
combines four lenses: a **Wardley map** to understand where value sits and how mature each component is,
**market sizing** to bound the prize, a **North-Star metric plus HEART** to define what success means, and
**RICE** to rank candidate bets. The output is an opportunity brief that an investment-minded reader can
act on — honest about assumptions, because every number here is a modeled estimate, not a measured fact.

## Steps
1. **Map the value chain (Wardley).**
   - Place user-visible needs at the top of the value chain and trace the components they depend on
     downward (the anchor-to-component structure).
   - Position each component along the evolution axis: Genesis → Custom-built → Product/rental → Commodity.
     This reveals where to build (novel, defensible) versus buy (commodity), and where the strategic
     opportunity actually lives.
2. **Size the market (TAM/SAM/SOM).**
   - **TAM** (total addressable market): the whole demand if you captured 100%.
   - **SAM** (serviceable addressable market): the slice your model can actually serve.
   - **SOM** (serviceable obtainable market): the share you can realistically win near-term.
   - State each as a range with its core assumptions; sizing is a triangulation of imperfect inputs, so
     show top-down and bottom-up estimates where possible and reconcile the gap.
3. **Define success — North-Star metric + HEART.**
   - Choose one **North-Star metric** that captures the core value delivered to users (a leading indicator
     of durable growth), not a vanity count.
   - Use **HEART** — Happiness, Engagement, Adoption, Retention, Task success — to derive the supporting
     signals and their Goals-Signals-Metrics so the North-Star is not measured in isolation.
4. **Enumerate and rank bets (RICE).**
   - List candidate bets, then score each: **Reach** (how many affected per period), **Impact** (effect
     size per user), **Confidence** (how sure you are, in %), **Effort** (person-time). Score = (Reach ×
     Impact × Confidence) ÷ Effort.
   - Confidence is the honesty dial: low-evidence bets MUST take a low confidence multiplier so speculation
     cannot outrank validated work.
5. **Assemble the brief.**
   - Synthesize map, sizing, success definition, and ranked bets into a single brief with an explicit
     recommendation and the assumptions it stands on.

## Constraints
- TAM/SAM/SOM figures are modeled estimates with error bars, never commitments; the agent MUST state the
  assumptions and show ranges rather than single confident numbers.
- RICE Confidence MUST honestly reflect evidence strength; the agent MUST NOT inflate Confidence to push a
  favored bet up the ranking, and flags any score resting on untested assumptions.
- The North-Star metric must measure delivered user value, not a vanity or gameable count; reject metrics
  that rise while users are worse off.
- A Wardley map is a hypothesis about the landscape, not ground truth; label uncertain component positions
  as such.

## Output Format
Produce an opportunity brief containing:
- A Wardley map description: the value chain with each component's evolution stage and the build/buy
  implication.
- TAM/SAM/SOM as ranges with their key assumptions and the top-down vs bottom-up reconciliation.
- The North-Star metric plus the HEART supporting signals (Goals-Signals-Metrics).
- A RICE-ranked table of candidate bets with each factor shown, the score, and a confidence note.
- A clear recommendation (pursue / pursue-with-conditions / decline) with the assumptions it depends on.

## Security & Guardrails

### 1. Skill Security
- **Risk**: Number-laundering — a desired conclusion is back-justified by tuning sizing assumptions or RICE
  Confidence; mitigation: the agent MUST expose every assumption and weight so the brief is reproducible,
  and refuse to emit a single headline figure without its supporting range.
- **Risk**: Vanity North-Star — a gameable metric (raw signups, page views) is chosen because it looks good;
  mitigation: the agent validates the metric against delivered user value and rejects ones that can rise
  while users are harmed.

### 2. System Integration Security
- **Risk**: Confidential-data leakage — sizing draws on internal financials, contracts, or non-public market
  intel; mitigation: the agent segregates confidential inputs, labels the brief with its sensitivity, and
  scrubs source-identifying detail from any externally shareable version.
- **Risk**: Over-trusted brief drives spend — downstream agents treat ranked bets as approved budget;
  mitigation: the agent marks the brief as a decision input requiring human sign-off and ties commitment to
  a separate financial gate such as `financial-governance.skill`.

### 3. LLM & Agent Guardrails
- **Risk**: Hallucinated market data — the model invents a plausible TAM figure or competitor statistic;
  mitigation: every quantitative claim must trace to a named input, and the agent labels any figure it
  cannot source as an explicit assumption to be validated, never as fact.
- **Risk**: Overconfidence framing — the model presents speculative estimates with false certainty;
  mitigation: the agent attaches confidence levels and ranges to all projections and states the dominant
  uncertainty that would most change the recommendation.

Files in this skill

  • accessibility.skill.md6.7 KB
  • adr-writer.skill.md5 KB
  • business-case.skill.md4.1 KB
  • change-management.skill.md6.1 KB
  • decompose.skill.md4.1 KB
  • design-thinking.skill.md3.9 KB
  • estimation-sizing.skill.md5.7 KB
  • evals/spec-writer.eval.yaml967 B
  • financial-governance.skill.md5.8 KB
  • green-software.skill.md3.2 KB
  • ideation-facilitation.skill.md5.7 KB
  • market-analysis.skill.md3.5 KB
  • opportunity-assessment.skill.md5.8 KB
  • product-analytics.skill.md6.1 KB
  • professional-practice.skill.md7.6 KB
  • req-elicitation.skill.md11.4 KB
  • req-review.skill.md11.7 KB
  • spec-analyze.skill.md5.2 KB
  • spec-writer.skill.md6.5 KB
  • stakeholder-management.skill.md3.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.