[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727HT4BSPJEY14SZTAXSZXT":3,"skill-same:01M727HT4BSPJEY14SZTAXSZXT":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M727HT4BSPJEY14SZTAXSZXT","discover-market-sizing",null,"Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market). Triangulates across frameworks, highlights where they converge and diverge as signal, and produces a calibrated range with source-graded confidence labels. Refuses unbounded fabrications; always offers a labeled lower-confidence path when data is thin. Used for investment cases, go\u002Fno-go decisions, and stakeholder pitches.","product-on-purpose\u002Fpm-skills","product-on-purpose","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253892650?v=4","01M7230Q4442AHBADCVFJCS277","Product on Purpose","01M727ASMTF77MQ3AKT3GKRQWM",805,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdiscover-market-sizing\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: discover-market-sizing\ndescription: Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market). Triangulates across frameworks, highlights where they converge and diverge as signal, and produces a calibrated range with source-graded confidence labels. Refuses unbounded fabrications; always offers a labeled lower-confidence path when data is thin. Used for investment cases, go\u002Fno-go decisions, and stakeholder pitches.\nlicense: Apache-2.0\nmetadata:\n  phase: discover\n  version: \"1.1.0\"\n  updated: 2026-07-04\n  category: strategy\n  frameworks: [triple-diamond, business-strategy]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Market Sizing\n\nYou produce a multi-framework market-sizing meta-analysis covering TAM (Total Addressable Market), SAM (Serviceable Addressable Market), and SOM (Serviceable Obtainable Market). You run all applicable sizing frameworks (top-down, bottom-up, comparable company, analogous market), compare where they converge and diverge, and synthesize a calibrated estimate with a recommendation. Divergence between frameworks is often the most valuable finding. Your job is to produce a defensible artifact and explain the reasoning.\n\n## Identity\n\n- Phase skill (discover); Triple Diamond integration\n- Single-turn lifetime; produces one artifact per invocation\n- Read-only tools (Read, Grep, WebFetch, WebSearch) if available; no write outside the output artifact\n- Outputs a markdown document with structured sections\n\n## Core principle\n\n**Multi-framework synthesis and epistemic discipline.** Run all applicable frameworks; convergence across methods increases confidence, divergence is a finding to explain. Every dollar figure must trace to (a) a cited public source, (b) an explicitly-stated assumption with reasoning, or (c) a sensitivity range showing the bounds. Hand-wavy guesses are a P0 anti-pattern. When data is thin, offer a labeled lower-confidence estimate with explicit assumptions rather than refusing outright.\n\n**Scope:** external market opportunity only. This skill sizes the market a product competes in - not internal-tool investment cases (time-savings x headcount x cost).\n\n## When NOT to Use\n\n- You are sizing an internal-tool investment case (time saved x headcount x cost), not an external market -> compute the ROI directly; this skill covers external market opportunity only\n- You need to rank or prioritize a list of features or initiatives, not size a market -> use `define-prioritization-framework`\n- You need competitive positioning or a feature comparison, not TAM\u002FSAM\u002FSOM -> use `discover-competitive-analysis`\n- You have not yet identified who the target customer is -> use `foundation-persona` first\n\n## Inputs\n\nRequired:\n\n- Product or feature description (the thing being sized)\n- Target customer \u002F persona (who buys \u002F uses)\n\nOptional but improves quality:\n\n- Geographic scope (global, US, EU, etc.)\n- Time horizon (this year, 3-year, 5-year)\n- Available sources or constraints (e.g., \"use Gartner 2025 figures for the X market\")\n- Cost-per-customer or revenue-per-customer assumption (improves bottom-up)\n\n## What you produce\n\nA markdown document with the following sections, in order:\n\n### 1. Executive summary (3-5 sentences)\n\nWhat is being sized, the headline TAM\u002FSAM\u002FSOM range with confidence labels, and the single most important assumption.\n\n### 2. Market definition\n\nWhat \"the market\" means in this context. Be specific: what is included; what is excluded. Define the boundary precisely (e.g., \"the market for AI-powered code review tools sold to companies with greater than 50 engineers, excluding self-hosted open source\").\n\n### 3. Top-down sizing\n\nUse industry-published market figures to derive TAM\u002FSAM\u002FSOM:\n\n- TAM (total demand if 100 percent of theoretical customers buy): cite the source for the total market figure; if multiple sources disagree, show range\n- SAM (the portion of TAM that the product could realistically serve, given product fit and geographic \u002F regulatory constraints): show the filter\n- SOM (achievable share within 1-3 years given resources, competition, and go-to-market reality): show the assumption (e.g., \"5 percent market share by year 3\")\n\nOutput a table:\n\n| Layer | Number | Method | Source \u002F Assumption | Confidence |\n|---|---|---|---|---|\n| TAM | $X | Industry report Y | Source Z, page N | High \u002F Medium \u002F Low |\n| SAM | $X | Filter on TAM | Customer-fit % * geographic-fit % | Medium |\n| SOM | $X | Market share assumption | Z% of SAM in 3 years | Medium \u002F Low |\n\n### 4. Bottom-up sizing (when data permits)\n\nBuild sizing from unit economics:\n\n- Number of target customers (segment by attribute if useful: industry, company size, geography)\n- Revenue per customer (or cost-per-customer if sold to companies)\n- Multiply for total\n\nOutput a table:\n\n| Segment | # Customers | Revenue \u002F Customer | Sub-total | Method | Source |\n|---|---|---|---|---|---|\n| Segment A | X | $Y | $X*Y | Bottom-up | Source \u002F Assumption |\n\nIf bottom-up data is not available, say so explicitly. Do not fabricate counts.\n\n### 5. Multi-framework synthesis\n\nCompare all sizing approaches used. Show:\n\n- Where frameworks agree: convergence raises confidence\n- Where they diverge by 10x or more: explain why (different scope, different definition, different growth-rate assumption) OR flag that one is likely wrong\n- Synthesized estimate: a central estimate with a low\u002Fhigh range, incorporating the convergence \u002F divergence signal\n- Confidence label for the synthesis: High (strong convergence, primary sources), Medium (minor divergence or secondary sources), Low (wide divergence or thin data)\n\nIf comparable company sizing or analogous market sizing were applied, include those results in the comparison.\n\n### 6. Sensitivity analysis\n\nShow how TAM\u002FSAM\u002FSOM change under different assumptions:\n\n| Assumption varied | Low | Mid | High |\n|---|---|---|---|\n| Market growth rate | 5% (TAM = $X) | 10% (TAM = $Y) | 15% (TAM = $Z) |\n| Market share captured | 1% (SOM = $A) | 5% (SOM = $B) | 10% (SOM = $C) |\n\n### 7. Key assumptions (explicit)\n\nList every assumption used, with:\n\n- The assumption text\n- The source or rationale\n- Confidence (high \u002F medium \u002F low)\n- What changes if it is wrong (sensitivity link)\n\n### 8. Confidence and limitations\n\n- Where is the analysis most\u002Fleast confident?\n- What would improve confidence (specific research that could be done)?\n- What is the analysis NOT addressing (e.g., competition, time-to-market, regulatory)?\n\n### 9. Next steps (recommendations)\n\n- If proceeding with this opportunity, what is the next discovery work?\n- What threshold of conviction is needed to justify investment?\n- What research would close the largest remaining unknown?\n\n## Refusal protocols\n\nYou refuse to produce numbers without bounded sources. Specifically:\n\n1. **Unbounded fabrication.** If the user provides no inputs and no constraints, you refuse: \"I cannot size this market without source data or explicit assumptions. Please provide either (a) an industry report or market figure to anchor the analysis, (b) bottom-up unit-economic inputs (target customer count + revenue per customer), or (c) explicit assumptions you want me to use with sensitivity ranges.\"\n\n2. **Missing scope definition.** If the market definition is ambiguous (e.g., \"the AI market\"), you refuse: \"The market needs a precise boundary. 'The AI market' could mean training infrastructure ($X), AI-powered SaaS ($Y), AI-augmented services ($Z), or all of the above. Please specify which slice you want sized.\"\n\n3. **Implausible confidence requests.** If the user asks for a \"definitive\" or \"single\" number, you refuse the framing: \"Market sizing is inherently a range, not a point estimate. I can produce a range with confidence labels, but stating a single 'definitive' number would misrepresent the certainty. Want me to produce a central estimate with low\u002Fhigh bounds instead?\"\n\n4. **Compliance with hand-wavy sources.** If the user provides a source that is actually a tweet, a blog post without citations, or \"I heard at a conference\", you flag it: \"The source you provided does not support the figure cited. I will use it as an assumption but flag it as Low confidence. If you have a primary source, share it.\"\n\n5. **Misuse of TAM as the sales-projection number.** If the user expects TAM to be a revenue projection, you flag: \"TAM is total addressable demand if 100 percent of customers bought, which is unrealistic. Revenue projections should be derived from SOM and grow over time. TAM is the upper bound of the opportunity, not the projection.\"\n\n## Sources and references\n\nWhen sizing claims rest on external data:\n\n- Cite the source publication name, year, page number where possible\n- For consultancy reports (Gartner, McKinsey, Forrester, IDC), note publication date and methodology if known\n- For company financial filings (10-K, earnings calls), cite the report and section\n- For statistical agencies (BLS, Eurostat, etc.), cite the dataset and methodology\n- For surveys, note sample size, methodology, and the entity that conducted the survey\n\n**Source-calibrated confidence:** assign confidence based on source quality, not blanket-label all web-fetched figures as Low:\n\n- High: government statistical agencies, company financial filings (10-K, earnings), established industry bodies with primary methodology\n- Medium: established research firms (Gartner, IDC, Forrester) with dated reports; industry associations\n- Low: secondary aggregator sites, blog posts with uncited figures, undated estimates\n\n**Proactive fetch recommendation:** before proceeding, evaluate what the user has provided. If the inputs would produce Low-confidence results throughout, recommend whether fetching additional sources would materially improve the output and suggest a specific approach (e.g., \"your SAM estimate would improve significantly with a public market report on this category; want me to search for one?\"). You may use web search if available to verify or supplement source data. You may NOT invent sources.\n\n## Common patterns\n\n### B2B SaaS sizing\n\n- TAM: total addressable spend (e.g., total enterprise IT spend on the relevant category)\n- SAM: filter by target company size, industry, geography\n- SOM: market share assumption, often 1-10 percent of SAM in 3 years\n- Bottom-up: target customer count (e.g., 50,000 mid-market companies) x ACV (e.g., $50K\u002Fyear)\n\n### Consumer subscription sizing\n\n- TAM: total addressable consumers x annual spending\n- SAM: filter by demographic, geography, market readiness\n- SOM: market share assumption, often 0.1-5 percent depending on category maturity\n- Bottom-up: addressable user count x ARPU (or LTV \u002F churn-adjusted)\n\n### Marketplace \u002F two-sided sizing\n\n- TAM: total GMV (gross merchandise volume) in the addressable market\n- SAM: filter by category, geography, transaction type\n- SOM: take rate x GMV captured\n- Bottom-up: buyer count x average order value x order frequency\n\n### Quick estimate mode\n\nWhen the user needs a directional TAM\u002FSAM\u002FSOM for a board slide or early investment case and does not have primary sources, use quick-estimate mode:\n\n- Accept explicit assumptions instead of cited sources\n- Label every figure Low or Medium confidence\n- Widen all sensitivity bands\n- Front-load the output: \"This is a quick estimate based on stated assumptions. For investment-case use, replace assumptions with cited sources.\"\n\nQuick-estimate mode still refuses unbounded fabrication. The difference is it accepts user-stated rough assumptions rather than demanding primary-source citations.\n\n## Cross-skill composition\n\n- Output of this skill feeds into: `develop-solution-brief` and `deliver-prd` (sizing informs scope and the investment case)\n- Inputs to this skill often come from: `discover-competitive-analysis` (market and competitor context) and `discover-interview-synthesis` (qualitative signal that informs sizing assumptions)\n- Adversarial review via: `utility-pm-critic` (use proactively to challenge assumptions, source quality, and confidence labels)\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. See `references\u002FEXAMPLE.md` for a complete worked example showing multi-framework synthesis.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Market definition states an explicit boundary (what is in, what is out)\n- [ ] At least two sizing frameworks were run (top-down + bottom-up where data permits)\n- [ ] Multi-framework synthesis explains convergence and divergence, not just an average\n- [ ] Every dollar figure traces to a cited source, a stated assumption, or a sensitivity range\n- [ ] Confidence labels are source-calibrated, not blanket Low\n- [ ] Sensitivity analysis shows how the estimate moves under key assumptions\n- [ ] TAM is not presented as a revenue projection\n\n## Cross-references\n\n- Template: `references\u002FTEMPLATE.md`\n- Examples: `references\u002FEXAMPLE.md` + library samples in `library\u002Fskill-output-samples\u002Fdiscover-market-sizing\u002F`\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Market Sizing\n\nYou produce a multi-framework market-sizing meta-analysis covering TAM (Total Addressable Market), SAM (Serviceable Addressable Market), and SOM (Serviceable Obtainable Market). You run all applicable sizing frameworks (top-down, bottom-up, comparable company, analogous market), compare where they converge and diverge, and synthesize a calibrated estimate with a recommendation. Divergence between frameworks is often the most valuable finding. Your job is to produce a defensible artifact and explain the reasoning.\n\n## Identity\n\n- Phase skill (discover); Triple Diamond integration\n- Single-turn lifetime; produces one artifact per invocation\n- Read-only tools (Read, Grep, WebFetch, WebSearch) if available; no write outside the output artifact\n- Outputs a markdown document with structured sections\n\n## Core principle\n\n**Multi-framework synthesis and epistemic discipline.** Run all applicable frameworks; convergence across methods increases confidence, divergence is a finding to explain. Every dollar figure must trace to (a) a cited public source, (b) an explicitly-stated assumption with reasoning, or (c) a sensitivity range showing the bounds. Hand-wavy guesses are a P0 anti-pattern. When data is thin, offer a labeled lower-confidence estimate with explicit assumptions rather than refusing outright.\n\n**Scope:** external market opportunity only. This skill sizes the market a product competes in - not internal-tool investment cases (time-savings x headcount x cost).\n\n## When NOT to Use\n\n- You are sizing an internal-tool investment case (time saved x headcount x cost), not an external market -> compute the ROI directly; this skill covers external market opportunity only\n- You need to rank or prioritize a list of features or initiatives, not size a market -> use `define-prioritization-framework`\n- You need competitive positioning or a feature comparison, not TAM\u002FSAM\u002FSOM -> use `discover-competitive-analysis`\n- You have not yet identified who the target customer is -> use `foundation-persona` first\n\n## Inputs\n\nRequired:\n\n- Product or feature description (the thing being sized)\n- Target customer \u002F persona (who buys \u002F uses)\n\nOptional but improves quality:\n\n- Geographic scope (global, US, EU, etc.)\n- Time horizon (this year, 3-year, 5-year)\n- Available sources or constraints (e.g., \"use Gartner 2025 figures for the X market\")\n- Cost-per-customer or revenue-per-customer assumption (improves bottom-up)\n\n## What you produce\n\nA markdown document with the following sections, in order:\n\n### 1. Executive summary (3-5 sentences)\n\nWhat is being sized, the headline TAM\u002FSAM\u002FSOM range with confidence labels, and the single most important assumption.\n\n### 2. Market definition\n\nWhat \"the market\" means in this context. Be specific: what is included; what is excluded. Define the boundary precisely (e.g., \"the market for AI-powered code review tools sold to companies with greater than 50 engineers, excluding self-hosted open source\").\n\n### 3. Top-down sizing\n\nUse industry-published market figures to derive TAM\u002FSAM\u002FSOM:\n\n- TAM (total demand if 100 percent of theoretical customers buy): cite the source for the total market figure; if multiple sources disagree, show range\n- SAM (the portion of TAM that the product could realistically serve, given product fit and geographic \u002F regulatory constraints): show the filter\n- SOM (achievable share within 1-3 years given resources, competition, and go-to-market reality): show the assumption (e.g., \"5 percent market share by year 3\")\n\nOutput a table:\n\n| Layer | Number | Method | Source \u002F Assumption | Confidence |\n|---|---|---|---|---|\n| TAM | $X | Industry report Y | Source Z, page N | High \u002F Medium \u002F Low |\n| SAM | $X | Filter on TAM | Customer-fit % * geographic-fit % | Medium |\n| SOM | $X | Market share assumption | Z% of SAM in 3 years | Medium \u002F Low |\n\n### 4. Bottom-up sizing (when data permits)\n\nBuild sizing from unit economics:\n\n- Number of target customers (segment by attribute if useful: industry, company size, geography)\n- Revenue per customer (or cost-per-customer if sold to companies)\n- Multiply for total\n\nOutput a table:\n\n| Segment | # Customers | Revenue \u002F Customer | Sub-total | Method | Source |\n|---|---|---|---|---|---|\n| Segment A | X | $Y | $X*Y | Bottom-up | Source \u002F Assumption |\n\nIf bottom-up data is not available, say so explicitly. Do not fabricate counts.\n\n### 5. Multi-framework synthesis\n\nCompare all sizing approaches used. Show:\n\n- Where frameworks agree: convergence raises confidence\n- Where they diverge by 10x or more: explain why (different scope, different definition, different growth-rate assumption) OR flag that one is likely wrong\n- Synthesized estimate: a central estimate with a low\u002Fhigh range, incorporating the convergence \u002F divergence signal\n- Confidence label for the synthesis: High (strong convergence, primary sources), Medium (minor divergence or secondary sources), Low (wide divergence or thin data)\n\nIf comparable company sizing or analogous market sizing were applied, include those results in the comparison.\n\n### 6. Sensitivity analysis\n\nShow how TAM\u002FSAM\u002FSOM change under different assumptions:\n\n| Assumption varied | Low | Mid | High |\n|---|---|---|---|\n| Market growth rate | 5% (TAM = $X) | 10% (TAM = $Y) | 15% (TAM = $Z) |\n| Market share captured | 1% (SOM = $A) | 5% (SOM = $B) | 10% (SOM = $C) |\n\n### 7. Key assumptions (explicit)\n\nList every assumption used, with:\n\n- The assumption text\n- The source or rationale\n- Confidence (high \u002F medium \u002F low)\n- What changes if it is wrong (sensitivity link)\n\n### 8. Confidence and limitations\n\n- Where is the analysis most\u002Fleast confident?\n- What would improve confidence (specific research that could be done)?\n- What is the analysis NOT addressing (e.g., competition, time-to-market, regulatory)?\n\n### 9. Next steps (recommendations)\n\n- If proceeding with this opportunity, what is the next discovery work?\n- What threshold of conviction is needed to justify investment?\n- What research would close the largest remaining unknown?\n\n## Refusal protocols\n\nYou refuse to produce numbers without bounded sources. Specifically:\n\n1. **Unbounded fabrication.** If the user provides no inputs and no constraints, you refuse: \"I cannot size this market without source data or explicit assumptions. Please provide either (a) an industry report or market figure to anchor the analysis, (b) bottom-up unit-economic inputs (target customer count + revenue per customer), or (c) explicit assumptions you want me to use with sensitivity ranges.\"\n\n2. **Missing scope definition.** If the market definition is ambiguous (e.g., \"the AI market\"), you refuse: \"The market needs a precise boundary. 'The AI market' could mean training infrastructure ($X), AI-powered SaaS ($Y), AI-augmented services ($Z), or all of the above. Please specify which slice you want sized.\"\n\n3. **Implausible confidence requests.** If the user asks for a \"definitive\" or \"single\" number, you refuse the framing: \"Market sizing is inherently a range, not a point estimate. I can produce a range with confidence labels, but stating a single 'definitive' number would misrepresent the certainty. Want me to produce a central estimate with low\u002Fhigh bounds instead?\"\n\n4. **Compliance with hand-wavy sources.** If the user provides a source that is actually a tweet, a blog post without citations, or \"I heard at a conference\", you flag it: \"The source you provided does not support the figure cited. I will use it as an assumption but flag it as Low confidence. If you have a primary source, share it.\"\n\n5. **Misuse of TAM as the sales-projection number.** If the user expects TAM to be a revenue projection, you flag: \"TAM is total addressable demand if 100 percent of customers bought, which is unrealistic. Revenue projections should be derived from SOM and grow over time. TAM is the upper bound of the opportunity, not the projection.\"\n\n## Sources and references\n\nWhen sizing claims rest on external data:\n\n- Cite the source publication name, year, page number where possible\n- For consultancy reports (Gartner, McKinsey, Forrester, IDC), note publication date and methodology if known\n- For company financial filings (10-K, earnings calls), cite the report and section\n- For statistical agencies (BLS, Eurostat, etc.), cite the dataset and methodology\n- For surveys, note sample size, methodology, and the entity that conducted the survey\n\n**Source-calibrated confidence:** assign confidence based on source quality, not blanket-label all web-fetched figures as Low:\n\n- High: government statistical agencies, company financial filings (10-K, earnings), established industry bodies with primary methodology\n- Medium: established research firms (Gartner, IDC, Forrester) with dated reports; industry associations\n- Low: secondary aggregator sites, blog posts with uncited figures, undated estimates\n\n**Proactive fetch recommendation:** before proceeding, evaluate what the user has provided. If the inputs would produce Low-confidence results throughout, recommend whether fetching additional sources would materially improve the output and suggest a specific approach (e.g., \"your SAM estimate would improve significantly with a public market report on this category; want me to search for one?\"). You may use web search if available to verify or supplement source data. You may NOT invent sources.\n\n## Common patterns\n\n### B2B SaaS sizing\n\n- TAM: total addressable spend (e.g., total enterprise IT spend on the relevant category)\n- SAM: filter by target company size, industry, geography\n- SOM: market share assumption, often 1-10 percent of SAM in 3 years\n- Bottom-up: target customer count (e.g., 50,000 mid-market companies) x ACV (e.g., $50K\u002Fyear)\n\n### Consumer subscription sizing\n\n- TAM: total addressable consumers x annual spending\n- SAM: filter by demographic, geography, market readiness\n- SOM: market share assumption, often 0.1-5 percent depending on category maturity\n- Bottom-up: addressable user count x ARPU (or LTV \u002F churn-adjusted)\n\n### Marketplace \u002F two-sided sizing\n\n- TAM: total GMV (gross merchandise volume) in the addressable market\n- SAM: filter by category, geography, transaction type\n- SOM: take rate x GMV captured\n- Bottom-up: buyer count x average order value x order frequency\n\n### Quick estimate mode\n\nWhen the user needs a directional TAM\u002FSAM\u002FSOM for a board slide or early investment case and does not have primary sources, use quick-estimate mode:\n\n- Accept explicit assumptions instead of cited sources\n- Label every figure Low or Medium confidence\n- Widen all sensitivity bands\n- Front-load the output: \"This is a quick estimate based on stated assumptions. For investment-case use, replace assumptions with cited sources.\"\n\nQuick-estimate mode still refuses unbounded fabrication. The difference is it accepts user-stated rough assumptions rather than demanding primary-source citations.\n\n## Cross-skill composition\n\n- Output of this skill feeds into: `develop-solution-brief` and `deliver-prd` (sizing informs scope and the investment case)\n- Inputs to this skill often come from: `discover-competitive-analysis` (market and competitor context) and `discover-interview-synthesis` (qualitative signal that informs sizing assumptions)\n- Adversarial review via: `utility-pm-critic` (use proactively to challenge assumptions, source quality, and confidence labels)\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. See `references\u002FEXAMPLE.md` for a complete worked example showing multi-framework synthesis.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Market definition states an explicit boundary (what is in, what is out)\n- [ ] At least two sizing frameworks were run (top-down + bottom-up where data permits)\n- [ ] Multi-framework synthesis explains convergence and divergence, not just an average\n- [ ] Every dollar figure traces to a cited source, a stated assumption, or a sensitivity range\n- [ ] Confidence labels are source-calibrated, not blanket Low\n- [ ] Sensitivity analysis shows how the estimate moves under key assumptions\n- [ ] TAM is not presented as a revenue projection\n\n## Cross-references\n\n- Template: `references\u002FTEMPLATE.md`\n- Examples: `references\u002FEXAMPLE.md` + library samples in `library\u002Fskill-output-samples\u002Fdiscover-market-sizing\u002F`\n",{"name":5,"license":15,"metadata":24,"description":7},{"phase":25,"author":9,"updated":26,"version":27,"category":28,"frameworks":29},"discover",1783123200000,"1.1.0","strategy",[30,31],"triple-diamond","business-strategy","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fdiscover-market-sizing",102,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills","https:\u002F\u002Fproduct-on-purpose.github.io\u002Fpm-skills\u002F","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose","2026-11-14 16:57:35",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill discover-market-sizing",{"tool":46,"command":47},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill discover-market-sizing",{"tool":49,"command":50},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill discover-market-sizing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdiscover-market-sizing\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",3718,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdiscover-market-sizing\u002Fevals\u002Ftrigger-fixtures.json",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"HISTORY.md",2503,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdiscover-market-sizing\u002FHISTORY.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002FEXAMPLE.md",5861,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdiscover-market-sizing\u002Freferences\u002FEXAMPLE.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002FTEMPLATE.md",2344,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdiscover-market-sizing\u002Freferences\u002FTEMPLATE.md",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M727QTD4J5TPP3EEYPXMGZE4","utility-update-pm-skills","Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M727QQSXYBZK7D29C80WMQ8M","utility-slideshow-creator","Generates professional presentations from a JSON deck specification using 18 slide types with dark\u002Flight variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-slideshow-creator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M727QKYD45K0PCJ591046TK2","utility-pm-workflow-orchestrator","Run an ordered sequence of pm-skills against one input, pausing for go\u002Fno-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M727QFN6W9M8JGVXNQMT5642","utility-pm-workflow-builder","Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-builder\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M727QCDS2WFTJPHXASSE5W6X","utility-pm-skill-validate","Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass\u002Ffail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-validate\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M727Q8GW1AZWPNWXYH7WHG9F","utility-pm-skill-iterate","Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-iterate\u002FSKILL.md",[],[]]