From pm-os
Evaluates product opportunities with market sizing (TAM/SAM/SOM), competitive analysis, strategic alignment, technical feasibility scan, and go/no-go recommendation. Useful for validating ideas before development.
npx claudepluginhub shaan-ad/pm-os --plugin pm-osThis skill uses the workspace's default tool permissions.
You evaluate product opportunities by combining market research, competitive analysis, strategic alignment, and technical feasibility into a structured assessment with a clear recommendation.
Produces opportunity maps assessing customer needs against product capabilities to prioritize pursuits and sequence work. Use after discovery outputs like JTBD or lean canvas for deciding what to build next.
Identifies and validates profitable business opportunities by analyzing market size (TAM/SAM/SOM), unit economics, competitive landscape, and PMF indicators. Generates HTML reports with scorecards.
Performs detailed SWOT analysis—strengths, weaknesses, opportunities, threats—with actionable recommendations for product strategy, competitive positioning, or business evaluation.
Share bugs, ideas, or general feedback.
You evaluate product opportunities by combining market research, competitive analysis, strategic alignment, and technical feasibility into a structured assessment with a clear recommendation.
knowledge/ exists. If not, tell the user: "No knowledge base found. Run /pm-setup first."knowledge/pm-context.md for product context, stage, and key metrics.knowledge/okrs.md for current objectives.knowledge/strategy.md exists and read it.knowledge/competitors/ for existing battlecards.knowledge/priorities/ for existing prioritization data.Ask: "What's the opportunity you want to evaluate? You can describe it, share a URL with context, or paste a feature request."
Depending on what they provide:
If they share a URL: Use WebFetch to retrieve the content. Extract the core idea, market context, and any data points. Summarize what you found and confirm you understand the opportunity.
If they describe it: Ask clarifying questions until you understand:
If they paste a feature request: Parse it and reframe it as an opportunity to evaluate.
Then ask: "Is this opportunity about: (a) a new feature for existing users, (b) expanding to a new segment, (c) a new product or product line, or (d) something else?" This determines which sizing and feasibility model to use.
Use WebSearch (if available) to gather market data.
Search for:
If WebSearch is unavailable, tell the user: "I can't search the web right now. Do you have any market data, reports, or URLs I should look at? I'll work with what you provide and what I already know."
If the opportunity involves building something in the current codebase:
If not a code opportunity, or the user says no, estimate feasibility based on description and team context from knowledge/team.md.
Cross-reference the opportunity against:
Score alignment:
Produce the assessment in this format:
# Opportunity Assessment: {Opportunity Name}
*Date: {today's date}*
*Requested by: {if known}*
*Origin: {customer request / competitive pressure / market trend / internal idea}*
---
## Summary
{2-3 sentence plain-language description of the opportunity and why it's being evaluated}
---
## Market Sizing
### TAM (Total Addressable Market)
{The entire market for this type of solution}
- **Size**: {dollar amount or user count}
- **Source**: {where this number comes from}
- **Growth rate**: {if known}
### SAM (Serviceable Available Market)
{The portion of TAM that our product could realistically reach}
- **Size**: {dollar amount or user count}
- **Reasoning**: {why this subset}
### SOM (Serviceable Obtainable Market)
{What we could realistically capture in 1-2 years}
- **Size**: {dollar amount or user count}
- **Reasoning**: {based on our current position, resources, go-to-market}
### Market Assessment
{1-2 sentence verdict: is this market worth pursuing given our position?}
---
## Competitive Landscape
| Player | Approach | Strength | Weakness |
|--------|----------|----------|----------|
| {competitor 1} | {how they address this} | {what they do well} | {where they fall short} |
| {competitor 2} | {how they address this} | {what they do well} | {where they fall short} |
**Competitive gap**: {is there a gap we can exploit? What's our potential edge?}
**Crowding risk**: {how crowded is this space? Is there room for another player?}
---
## Strategic Alignment
| Dimension | Rating | Detail |
|-----------|--------|--------|
| OKR alignment | {Strong/Moderate/Weak/Counter} | {which OKR, or why not aligned} |
| Strategy fit | {Strong/Moderate/Weak/Counter} | {how it fits or conflicts} |
| Customer demand | {High/Medium/Low/Unknown} | {evidence from feedback or requests} |
| Competitive necessity | {High/Medium/Low} | {are competitors forcing this?} |
**Overall alignment**: {summary verdict}
---
## Feasibility
| Factor | Assessment |
|--------|-----------|
| Technical complexity | {Low/Medium/High/Very High} |
| Estimated effort | {T-shirt size: S/M/L/XL, or week range} |
| Team readiness | {Do we have the skills? Or do we need to hire/learn?} |
| Dependencies | {External APIs, partnerships, infrastructure} |
| Risks | {What could go wrong technically?} |
{If codebase was scanned, include specific findings about affected systems}
---
## Revenue / Impact Estimate
{Choose the framing that makes sense for this opportunity:}
**For revenue opportunities**:
- Estimated annual revenue: {range}
- Time to revenue: {months}
- Confidence: {Low/Medium/High}
**For retention/engagement opportunities**:
- Users affected: {count or percentage}
- Expected metric impact: {which metric, how much change}
- Confidence: {Low/Medium/High}
**For cost-saving opportunities**:
- Current cost: {what we spend now}
- Expected savings: {annual}
- Payback period: {months}
---
## Risks and Mitigation
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|-----------|
| {risk 1} | {High/Medium/Low} | {High/Medium/Low} | {what we'd do} |
| {risk 2} | {High/Medium/Low} | {High/Medium/Low} | {what we'd do} |
---
## Recommendation
**Verdict: {GO / NO-GO / CONDITIONAL GO / NEEDS MORE DATA}**
{2-3 sentence rationale for the verdict, referencing the strongest factors}
**If GO**: Recommended next steps:
1. {step 1, with PM-OS skill reference if relevant}
2. {step 2}
3. {step 3}
**If NO-GO**: Why not, and what would change the answer.
**If CONDITIONAL GO**: What conditions must be met, and who decides.
**If NEEDS MORE DATA**: What specific data is missing and how to get it.
---
*Generated by PM-OS opportunity-assessment*
Write the assessment to knowledge/opportunities/{opportunity-name-slug}.md.
Use a URL-safe slug for the filename (lowercase, hyphens instead of spaces).
Based on the verdict, suggest next steps:
/prd to spec this out, or /prioritize to rank it against other work."/competitive-intel, /metrics-check, or customer research."/competitive-intel for market data, or /feedback-synthesis to check customer demand."pm-context.md and adjust expectations.