From pm-copilot
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.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyThis skill uses the workspace's default tool permissions.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
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.
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.
Before sizing, ensure the opportunity is precisely framed:
Vague opportunities can't be sized accurately. Help the user tighten the definition if needed.
Estimate: how many users currently experience this problem?
Work through:
Affected users = Total base × Segment % × Frequency % × Severity %
If exact numbers aren't available, use ranges: low / mid / high estimate.
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?
Calculate a RICE score for prioritization:
RICE = (Reach × Impact × Confidence) / Effort
Present:
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).