Opportunity Sizing logo

Opportunity Sizing

Community
Productfculty-aipm
opportunity-sizing

Use this skill when the user asks to "size this opportunity", "how big is this problem", "opportunity sizing", "how many users are affected", "estimate the impact", "what's the ROI", "is this worth building", "how do I prioritize this against other opportunities", or wants to quantify the potential value of solving a specific problem. Do NOT use this skill for full market sizing (TAM/SAM/SOM) — use the market-users/tam-sizing skill for that.

Overview

PublisherProductfculty-aipm
RepositoryPM-Copilot-by-Product-Faculty
Skill nameopportunity-sizing
Stars
80
Forks
34
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the Opportunity Sizing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/opportunity-sizing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/opportunity-sizing .claude/skills/opportunity-sizing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Opportunity Sizing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Opportunity Sizing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Opportunity Sizing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Opportunity Sizing

You are helping the user size a specific product opportunity — not the total addressable market, but the realistic impact of solving a specific user problem within the current product context.

Framework: Lenny Rachitsky's opportunity sizing model, OST opportunity scoring, RICE framework.

Step 1 — Load Context

Read memory/user-profile.md for product stage, user base size, and current metrics. Read context/company/analytics-baseline.md for baseline metrics to anchor estimates. Read context/product/roadmap.md for prioritization context.

Step 2 — Define the Opportunity Precisely

Before sizing, ensure the opportunity is precisely framed:

  • Which user segment is affected?
  • What specific struggle or unmet need are we sizing?
  • What would users do differently if this problem were solved?

Vague opportunities can't be sized accurately. Help the user tighten the definition if needed.

Step 3 — Size the Affected Population

Estimate: how many users currently experience this problem?

Work through:

  1. Total user base: From memory or analytics baseline
  2. Segment filter: What % of users are in the affected segment?
  3. Frequency filter: Of those users, what % encounter this problem regularly (weekly or more)?
  4. Severity filter: Of those, what % are meaningfully blocked vs. mildly annoyed?

Affected users = Total base × Segment % × Frequency % × Severity %

If exact numbers aren't available, use ranges: low / mid / high estimate.

Step 4 — Estimate the Impact Per User

For affected users, estimate what solving the problem is worth:

Retention impact: Would solving this meaningfully reduce churn? If the product's 30-day retention is X%, what would it be if this problem were gone? Translate to: users retained × average lifetime value.

Engagement impact: Would solving this increase feature adoption or session frequency? Translate to: additional sessions × conversion rate.

Acquisition impact: Would solving this reduce a key friction point in activation or onboarding? Translate to: improvement in activation rate × new users/month.

Revenue impact (if applicable): Would solving this unlock a new pricing tier or reduce downgrade pressure?

Step 5 — RICE Score

Calculate a RICE score for prioritization:

  • Reach: How many users per quarter are affected? (Use Step 3 estimate)
  • Impact: How much does it move the key metric per user? (1 = minimal, 3 = moderate, 9 = massive)
  • Confidence: How confident are you in the Reach and Impact estimates? (20% = guess, 80% = validated)
  • Effort: How many person-weeks to build and ship?

RICE = (Reach × Impact × Confidence) / Effort

Step 6 — Output

Present:

  • Sizing estimate: low / mid / high range of affected users
  • Impact estimate: what metric moves and by how much (with confidence level)
  • RICE score and how it compares to other known roadmap items (if any are in memory)
  • Recommendation: is this large enough to prioritize? What would make it larger or smaller?
  • Key sizing assumption: what number, if wrong, would most change this analysis?

Note the difference between the opportunity size (how big the problem is) and the solution potential (how much of the problem your specific solution can actually solve).

Frequently asked questions

What does the Opportunity Sizing AI skill do?

Use this skill when the user asks to "size this opportunity", "how big is this problem", "opportunity sizing", "how many users are affected", "estimate the impact", "what's the ROI", "is this worth building", "how do I prioritize this against other opportunities", or wants to quantify the potential value of solving a specific problem. Do NOT use this skill for full market sizing (TAM/SAM/SOM) — use the market-users/tam-sizing skill for that.

Why use Opportunity Sizing on TypingMind?

Because you install it once and use it with any model. Opportunity Sizing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Opportunity Sizing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/opportunity-sizing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Opportunity Sizing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Opportunity Sizing?

As many as you like. As long as a model supports skills, you can use Opportunity Sizing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Opportunity Sizing AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇