[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A02RB4VEYEKFAXG3WYVREG":3,"skill-same:01M7A02RB4VEYEKFAXG3WYVREG":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7A02RB4VEYEKFAXG3WYVREG","beachhead-segment",null,"Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-go-to-market\u002Fskills\u002Fbeachhead-segment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: beachhead-segment\ndescription: \"Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.\"\n---\n# Beachhead Segment\n\n## Overview\nIdentify the first beachhead market segment for product launch. This skill evaluates potential market segments against key criteria to find your initial winning segment that enables fast PMF validation and adjacent expansion.\n\n## When to Use\n- Choosing a first market for your product\n- Targeting an initial customer segment\n- Planning initial market entry strategy\n- Deciding where to focus limited resources\n- Validating GTM assumptions with early adopters\n\n## Key Evaluation Criteria\n\n### 1. Burning Pain Point\nDoes this segment experience an acute, unmet problem?\n- Daily frustration with the status quo\n- Significant productivity loss or cost impact\n- Emotional urgency to find a solution\n- Current workarounds are expensive or fragile\n- Problem is getting worse over time\n\n### 2. Willingness to Pay\nDoes this segment have budget and motivation to pay for a solution?\n- Documented budget allocation for this problem area\n- ROI is clear and compelling (value > cost)\n- Economic impact of problem justifies solution cost\n- Decision-maker has autonomy or influence over budget\n- No free or DIY alternatives that fully satisfy need\n\n### 3. Winnable Market Share\nCan you realistically capture 60-70% of this segment in 3-18 months?\n- Segment is large enough but not oversaturated\n- Limited competition or easy differentiation\n- Market players are fragmented or complacent\n- Your product has clear competitive advantage\n- You have unique access or distribution advantage\n\n### 4. Referral Potential\nWill customers naturally refer or recommend to others?\n- Segment contains professional communities\n- Customers interact with adjacent segments (expansion opportunity)\n- High word-of-mouth culture in this industry\n- Network effects within the segment\n- Solving problem for one creates demand in adjacent segments\n\n## How It Works\n\n### Step 1: List Potential Segments\nBrainstorm all possible target segments:\n- Industry verticals (SaaS, healthcare, manufacturing, etc.)\n- Company size (SMB, mid-market, enterprise)\n- Job titles or roles\n- Geographic regions\n- Use cases or use-case variations\n- Customer maturity level\n\n### Step 2: Research Pain Points\nValidate burning pain in each segment:\n- Customer interviews and discovery calls\n- Problem validation through surveys\n- Market research and analyst reports\n- Competitor positioning and customer reviews\n- Quantify cost\u002Fimpact of the problem\n- Identify current workarounds and limitations\n\n### Step 3: Assess Willingness to Pay\nDetermine budget and economic viability:\n- Segment's budget for this problem category\n- ROI calculation (value gained vs cost)\n- Current spending on solutions or workarounds\n- Budget decision-making process\n- Typical deal size expectations\n- Pricing sensitivity in the segment\n\n### Step 4: Evaluate Winnability\nAssess realistic market share potential:\n- Total addressable market (TAM) size\n- Competitive landscape and positioning\n- Your differentiation or unfair advantage\n- Distribution access to this segment\n- Time and resources required\n- Market growth and momentum\n\n### Step 5: Identify Referral Pathways\nMap expansion opportunities:\n- Adjacent segments that reference segment influences\n- Network effects within the segment\n- Professional communities and associations\n- Customer-to-customer recommendations\n- Natural expansion path to adjacent markets\n- Viral or network effects from solving core pain\n\n### Step 6: Select Beachhead\nChoose your primary launch segment:\n- Highest combined score across four criteria\n- Most achievable for your current resources\n- Shortest path to PMF and revenue\n- Best reference for adjacent expansion\n- Most enthusiastic early customer cohort\n\n## Input Format\nUse $ARGUMENTS to pass:\n- Product description and capabilities\n- Initial market research and validation data\n- Potential segment options\n- Constraints and limitations\n- Timeline and resource constraints\n- Current customer data or feedback\n\n## Output\nA beachhead segment analysis including:\n- Top 3-5 recommended segments with scoring\n- Primary beachhead segment recommendation\n- Pain point validation and evidence\n- Willingness to pay assessment and pricing guidance\n- Realistic market share and revenue projections\n- Referral and expansion pathways to adjacent segments\n- 90-day customer acquisition plan for beachhead\n- Post-beachhead expansion roadmap\n\n## Framework\nBased on Geoffrey Moore's beachhead market strategy in \"Crossing the Chasm.\" Focuses on finding the smallest winnable, referenceable market that validates PMF and enables expansion.\n\n## Tips\n- Start absurdly specific. A niche beachhead is better than a vague mass market\n- Choose the segment most likely to evangelize your solution\n- Validate all four criteria with at least 10 customer interviews\n- Select segment with fastest path to revenue and references\n- Ensure beachhead can reference to adjacent market segments\n- Focus all resources on dominating the beachhead (not diluting efforts)\n- Plan exit from beachhead only after 60%+ market share\n\n---\n\n### Further Reading\n\n- [5 GTM Principles You Should Know as a PM](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002F5-gtm-principles-with-frameworks-templates)\n- [Product-Led Growth 101, Part 1\u002F2](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fproduct-led-growth-101-12)\n- [How to Design a Value Proposition Customers Can't Resist?](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-design-value-proposition-template)\n- [How to Achieve Product-Market Fit? Part I: Market and Value Proposition](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-achieve-the-product-market)\n","# Beachhead Segment\n\n## Overview\nIdentify the first beachhead market segment for product launch. This skill evaluates potential market segments against key criteria to find your initial winning segment that enables fast PMF validation and adjacent expansion.\n\n## When to Use\n- Choosing a first market for your product\n- Targeting an initial customer segment\n- Planning initial market entry strategy\n- Deciding where to focus limited resources\n- Validating GTM assumptions with early adopters\n\n## Key Evaluation Criteria\n\n### 1. Burning Pain Point\nDoes this segment experience an acute, unmet problem?\n- Daily frustration with the status quo\n- Significant productivity loss or cost impact\n- Emotional urgency to find a solution\n- Current workarounds are expensive or fragile\n- Problem is getting worse over time\n\n### 2. Willingness to Pay\nDoes this segment have budget and motivation to pay for a solution?\n- Documented budget allocation for this problem area\n- ROI is clear and compelling (value > cost)\n- Economic impact of problem justifies solution cost\n- Decision-maker has autonomy or influence over budget\n- No free or DIY alternatives that fully satisfy need\n\n### 3. Winnable Market Share\nCan you realistically capture 60-70% of this segment in 3-18 months?\n- Segment is large enough but not oversaturated\n- Limited competition or easy differentiation\n- Market players are fragmented or complacent\n- Your product has clear competitive advantage\n- You have unique access or distribution advantage\n\n### 4. Referral Potential\nWill customers naturally refer or recommend to others?\n- Segment contains professional communities\n- Customers interact with adjacent segments (expansion opportunity)\n- High word-of-mouth culture in this industry\n- Network effects within the segment\n- Solving problem for one creates demand in adjacent segments\n\n## How It Works\n\n### Step 1: List Potential Segments\nBrainstorm all possible target segments:\n- Industry verticals (SaaS, healthcare, manufacturing, etc.)\n- Company size (SMB, mid-market, enterprise)\n- Job titles or roles\n- Geographic regions\n- Use cases or use-case variations\n- Customer maturity level\n\n### Step 2: Research Pain Points\nValidate burning pain in each segment:\n- Customer interviews and discovery calls\n- Problem validation through surveys\n- Market research and analyst reports\n- Competitor positioning and customer reviews\n- Quantify cost\u002Fimpact of the problem\n- Identify current workarounds and limitations\n\n### Step 3: Assess Willingness to Pay\nDetermine budget and economic viability:\n- Segment's budget for this problem category\n- ROI calculation (value gained vs cost)\n- Current spending on solutions or workarounds\n- Budget decision-making process\n- Typical deal size expectations\n- Pricing sensitivity in the segment\n\n### Step 4: Evaluate Winnability\nAssess realistic market share potential:\n- Total addressable market (TAM) size\n- Competitive landscape and positioning\n- Your differentiation or unfair advantage\n- Distribution access to this segment\n- Time and resources required\n- Market growth and momentum\n\n### Step 5: Identify Referral Pathways\nMap expansion opportunities:\n- Adjacent segments that reference segment influences\n- Network effects within the segment\n- Professional communities and associations\n- Customer-to-customer recommendations\n- Natural expansion path to adjacent markets\n- Viral or network effects from solving core pain\n\n### Step 6: Select Beachhead\nChoose your primary launch segment:\n- Highest combined score across four criteria\n- Most achievable for your current resources\n- Shortest path to PMF and revenue\n- Best reference for adjacent expansion\n- Most enthusiastic early customer cohort\n\n## Input Format\nUse $ARGUMENTS to pass:\n- Product description and capabilities\n- Initial market research and validation data\n- Potential segment options\n- Constraints and limitations\n- Timeline and resource constraints\n- Current customer data or feedback\n\n## Output\nA beachhead segment analysis including:\n- Top 3-5 recommended segments with scoring\n- Primary beachhead segment recommendation\n- Pain point validation and evidence\n- Willingness to pay assessment and pricing guidance\n- Realistic market share and revenue projections\n- Referral and expansion pathways to adjacent segments\n- 90-day customer acquisition plan for beachhead\n- Post-beachhead expansion roadmap\n\n## Framework\nBased on Geoffrey Moore's beachhead market strategy in \"Crossing the Chasm.\" Focuses on finding the smallest winnable, referenceable market that validates PMF and enables expansion.\n\n## Tips\n- Start absurdly specific. A niche beachhead is better than a vague mass market\n- Choose the segment most likely to evangelize your solution\n- Validate all four criteria with at least 10 customer interviews\n- Select segment with fastest path to revenue and references\n- Ensure beachhead can reference to adjacent market segments\n- Focus all resources on dominating the beachhead (not diluting efforts)\n- Plan exit from beachhead only after 60%+ market share\n\n---\n\n### Further Reading\n\n- [5 GTM Principles You Should Know as a PM](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002F5-gtm-principles-with-frameworks-templates)\n- [Product-Led Growth 101, Part 1\u002F2](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fproduct-led-growth-101-12)\n- [How to Design a Value Proposition Customers Can't Resist?](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-design-value-proposition-template)\n- [How to Achieve Product-Market Fit? Part I: Market and Value Proposition](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-achieve-the-product-market)\n",{"name":5,"description":7},"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fpm-go-to-market\u002Fskills\u002Fbeachhead-segment","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kongnakornna\u002Fgolangapi --skill beachhead-segment",{"tool":38,"command":39},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill beachhead-segment",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill beachhead-segment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-go-to-market\u002Fskills\u002Fbeachhead-segment\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]