go-to-market-plan

ognjengt/founder-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/ognjengt/founder-skills --skill go-to-market-plan
0 commentsdiscussion
summary

Analyze the founder's business and current stage to deliver 3 specific, actionable go-to-market strategies that will drive measurable market penetration and customer acquisition.

skill.md

Go-to-Market Plan

Purpose

Analyze the founder's business and current stage to deliver 3 specific, actionable go-to-market strategies that will drive measurable market penetration and customer acquisition.


Execution Logic

Check $ARGUMENTS first to determine execution mode:

If $ARGUMENTS is empty or not provided:

Respond with: "go-to-market-plan loaded, proceed with details about your product, target market, or current launch situation"

Then wait for the user to provide their requirements in the next message.

If $ARGUMENTS contains content:

Proceed immediately to Task Execution (skip the "loaded" message).


Task Execution

When user requirements are available (either from initial $ARGUMENTS or follow-up message):

1. Read Business Context

Check if FOUNDER_CONTEXT.md exists in the project root.

  • If it exists: Read it and extract: company name, industry, target audience, value proposition, products/services, business stage, competitors, pricing model, unique advantages.
  • If it doesn't exist: Proceed to Step 2 and gather this information through questions.

2. Diagnose GTM Readiness

Evaluate whether you have enough information to produce high-confidence, actionable go-to-market strategies:

Required information to proceed without questions:

  • What problem the product solves (core value proposition)
  • Who the ideal customer is (specific ICP, not "small businesses" or "everyone")
  • Product readiness stage (MVP, beta, ready to scale, etc.)
  • Competitive landscape (who else solves this, how you're different)
  • Distribution model (direct, channel partners, marketplace, etc.)
  • Pricing strategy (freemium, paid, enterprise, etc.)
  • Current market position (pre-launch, launched but struggling, ready to scale)
  • Available resources (team, budget, runway)

If you have enough context: Proceed directly to Step 4.

If critical information is missing: Proceed to Step 3.

3. Ask Diagnostic Questions (When Needed)

Use the AskUserQuestion tool to gather missing information. Ask between 3-10 questions based on what's needed:

Core GTM questions:

  • What stage is your product at right now? (Idea, MVP, beta, launched, scaling)
  • Who is your ideal first customer? (Be specific: role, company size, industry, pain point)
  • What's the core problem your product solves? How do people solve it today?
  • How do customers currently discover solutions like yours?
  • What's your biggest struggle with go-to-market right now?
  • What have you already tried for customer acquisition? What worked? What didn't?
  • What resources do you have available? (Budget, team, timeline, network)

Context-specific questions:

  • For pre-launch: "Have you validated product-market fit? How many people have you talked to?"
  • For launched but struggling: "Where are you getting customers today? What's your current CAC vs. LTV?"
  • For scaling: "What channels are working? What's your constraint to 10x growth?"
  • For competitive positioning: "Who are your top 3 competitors? Why would someone choose you over them?"
  • For pricing clarity: "Have you tested pricing? What signals indicate customers will pay this amount?"

IMPORTANT: Only ask questions for information you truly need. Don't ask for information you can infer from FOUNDER_CONTEXT.md or the user's initial message.

4. Analyze Market Entry Strategy

Based on the context gathered, analyze:

  1. Product-Market Fit Status: Do they have it? How do you know?
  2. Market Entry Point: Where is the wedge? (Specific segment, use case, or channel)
  3. Competitive Positioning: What's the unique angle that cuts through noise?
  4. Distribution Channels: Where does the ICP actually spend time and make buying decisions?
  5. Go-to-Market Motion: Product-led, sales-led, community-led, or hybrid?
  6. Market Timing: Why now? What's changed in the market or technology?

Critical analysis principles:

  • Start narrow, expand later: Best GTM starts with a tight, underserved segment
  • Channel-product fit matters more than product-market fit early on: Great product in wrong channel = no traction
  • Identify unfair advantages: Network, expertise, distribution, brand, technology
  • Find the "bowling pin" strategy: Which customer segment unlocks adjacent segments?
  • Validate before scaling: Don't build GTM for hypothetical customers

5. Generate 3 Go-to-Market Strategies

Create exactly 3 GTM strategies, ranked by fit and impact:

Selection criteria:

  • Specificity: Is this concrete enough to execute this week?
  • Channel-market fit: Will the ICP actually see this in their buying journey?
  • Differentiation: Does this position you uniquely vs. competitors?
  • Scalability: Can this grow beyond the first 10 customers?
  • Resource fit: Can they execute with current team/budget/capabilities?
  • Confidence: Only recommend if you're confident it will work for THIS product and market

For each strategy, write:

Part A — The Strategy (What & Why)

  • One-line strategy name
  • 2-3 sentences explaining WHAT the GTM approach is and WHY it fits this product/market
  • Reference the specific market wedge, competitive angle, or channel advantage it leverages

Part B — The Exact Playbook (How)

  • Step-by-step execution plan with specific actions
  • Use their actual product name, ICP details, and market specifics
  • Include concrete details: which channels, which messaging, which segments, which metrics to track
  • Specify timeline and expected milestones

Part C — First Action (Do This Today)

  • One specific task they can complete in the next 30-60 minutes
  • Concrete enough that there's no ambiguity about what to do

6. Format and Verify

  • Structure output according to Output Format section
  • Complete Quality Checklist self-verification before presenting output

Writing Rules

Hard constraints. No interpretation.

Core Rules

  • Zero generic GTM advice. Every strategy must be specific to THIS product and market.
  • Use actual product names, ICP details, market specifics, and competitive positioning.
  • Lead with the highest-fit strategy first (not necessarily most innovative, but most likely to work).
  • Every strategy must include a concrete playbook, not just a concept.
  • Specify metrics to track for each strategy.
  • No motivational fluff. Only actionable GTM strategy.
  • Active voice only.
  • Strategies must be executable within their resource constraints.

Specificity Rules

  • BAD: "Use content marketing"

  • GOOD: "Write 1 deep-dive case study per week showing how [Product] helped [Specific ICP] solve [Specific Problem]. Post on LinkedIn targeting [Job Titles]. Include ROI metrics. Repurpose into email sequence for outbound. Goal: 500 views/post, 20 inbound leads/month."

  • BAD: "Build a community"

  • GOOD: "Launch a private Slack community for [Specific ICP] called '[Community Name]'. Seed it with 20 hand-picked customers. Host weekly 'Office Hours' where members can ask questions about [Problem Space]. Incentivize referrals: invite 3 peers = lifetime discount. Goal: 100 members in 60 days, 30% weekly active."

  • BAD: "Partner with influencers"

  • GOOD: "Identify 10 YouTubers with 50k-200k subscribers in [Industry] who cover [Topic]. Reach out with free access to [Product] + $500 flat fee for honest review video. Track: views, click-through rate, signups from each video. Goal: 3 partnerships, 500+ signups in 90 days."

Context-Based Adaptation

  • Pre-product-market fit: Focus on validation tactics (customer interviews, pilot programs, design partnerships, early adopter communities)

  • Post-product-market fit, pre-scale: Focus on repeatable acquisition (content engine, outbound playbook, referral loops, strategic partnerships)

  • Scaling stage: Focus on channel diversification, market expansion, brand building, enterprise upmarket moves

  • B2B SaaS: Prioritize outbound, content, product-led growth, partnerships, vertical events

  • B2C apps: Prioritize app store optimization, influencer marketing, viral loops, paid social

  • Marketplace: Prioritize supply-side first (harder to acquire), demand follows

  • Developer tools: Prioritize open source, technical content, developer communities, product-led growth

  • Category creation: Focus on education-first content, thought leadership, category naming/framing

  • Competitive market: Focus on wedge positioning, differentiated messaging, switching incentives

Quality Filters

Before finalizing ANY strategy, ask:

  • Is this specific to THIS product and market, or could it apply to any company?
  • Would the ICP actually see/engage with this in their buying journey?
  • Does this leverage an unfair advantage or unique positioning?
  • Can they execute this with current resources?
  • Would I personally bet money that this will produce traction?
  • If the answer to any is "no" → rewrite or replace the strategy.

Output Format

## Your 3 Go-to-Market Strategies

Based on [Product Name]'s current stage and market position, here are your 3 best go-to-market strategies:

---

### Strategy 1: [Strategy Name]

**The Strategy:**
[2-3 sentences: What the GTM approach is, why it fits this product/market, what advantage it leverages]

**The Exact Playbook:**

**Step 1:** [Specific action with details]
**Step 2:** [Specific action with details]
**Step 3:** [Specific action with details]
**Step 4:** [Specific action with details]

**Metrics to Track:**
- [Specific metric 1]
- [Specific metric 2]
- [Specific metric 3]

**Expected Milestones:**
[Concrete outcomes with timeline, e.g., "50 qualified leads within 30 days, 10 customers by day 60"]

**Do This Today:**
[One 30-60 minute action they can take immediately]

---

### Strategy 2: [Strategy Name]

**The Strategy:**
[...]

**The Exact Playbook:**
[...]

**Metrics to Track:**
[...]

**Expected Milestones:**
[...]

**Do This Today:**
[...]

---

### Strategy 3: [Strategy Name]

**The Strategy:**
[...]

**The Exact Playbook:**
[...]

**Metrics to Track:**
[...]

**Expected Milestones:**
[...]

**Do This Today:**
[...]

---

## Execution Priority

**Start with:** Strategy [X] — [One sentence explaining why this is the highest priority right now]

**Why this order:** [2-3 sentences explaining the strategic sequencing — why doing these in this order maximizes market penetration and learning]

---

## Success Criteria

You'll know these strategies are working when:
- [Specific metric/outcome 1 with timeline]
- [Specific metric/outcome 2 with timeline]
- [Specific metric/outcome 3 with timeline]

If you don't see these results, revisit your execution or pivot to a different market segment.

Example:

## Your 3 Go-to-Market Strategies

Based on DevAnalytics's current stage (MVP launched, 12 beta users, targeting engineering managers at Series A-C startups), here are your 3 best go-to-market strategies:

---

### Strategy 1: Design Partnership Program with 5 Target Companies

**The Strategy:**
Position DevAnalytics as a co-creation partner for engineering leaders at high-growth startups who are struggling with team productivity visibility. Instead of selling a finished product, offer to build custom dashboards alongside 5 carefully selected companies in exchange for case studies and testimonials. This validates product-market fit, generates social proof, and creates evangelists who will refer you to peers.

**The Exact Playbook:**

**Step 1:** Identify 5 Series A-C startups (50-150 employees) in your network or LinkedIn 2nd connections who recently raised funding and are likely hiring aggressively. Focus on companies using your tech stack (GitHub, Jira, Linear).

**Step 2:** Craft a personalized outreach message referencing their recent funding announcement: "Congrats on the Series B. As you scale engineering from 20 to 50, visibility into team productivity becomes critical. I'm building DevAnalytics specifically for this problem. Would you be open to a 6-week design partnership where we build custom dashboards for your team in exchange for feedback and a case study?"

**Step 3:** For accepted partnerships, conduct weekly 45-minute calls to understand their specific metrics needs, build dashboards collaboratively, and iterate based on feedback.

**Step 4:** Document each partnership as a case study showing: problem faced, metrics tracked, decisions made based on DevAnalytics data, and quantified outcomes (e.g., "Reduced deployment time by 30%").

**Metrics to Track:**
- Outreach sent: 20 (to get 5 partnerships)
- Partnership acceptance rate (goal: 25%)
- Weekly active users per partnership (goal: >70%)
- Case study completion rate (goal: 100%)

**Expected Milestones:**
5 active design partnerships within 30 days, 3 completed case studies by day 60, 2 paid conversions by day 90.

**
how to use go-to-market-plan

How to use go-to-market-plan on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add go-to-market-plan
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/ognjengt/founder-skills --skill go-to-market-plan

The skills CLI fetches go-to-market-plan from GitHub repository ognjengt/founder-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/go-to-market-plan

Reload or restart Cursor to activate go-to-market-plan. Access the skill through slash commands (e.g., /go-to-market-plan) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.425 reviews
  • Ganesh Mohane· Dec 4, 2024

    go-to-market-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Nikhil Lopez· Dec 4, 2024

    We added go-to-market-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 23, 2024

    go-to-market-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aisha Tandon· Nov 23, 2024

    Keeps context tight: go-to-market-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Pratham Ware· Oct 14, 2024

    Keeps context tight: go-to-market-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ishan Nasser· Oct 14, 2024

    go-to-market-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Jin Mensah· Sep 9, 2024

    We added go-to-market-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Piyush G· Sep 5, 2024

    I recommend go-to-market-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Liam Farah· Aug 28, 2024

    go-to-market-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Shikha Mishra· Aug 24, 2024

    Useful defaults in go-to-market-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 25

1 / 3