go-to-market-plan

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 90bc6f1424df · 23 Oct 2026Report an issue or request a re-scan

• Publisherognjengt GitHub userOwner of the repository this skill is read from
• Source folderognjengt/founder-skills/skills/go-to-market-planThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict90bc6f1424dfA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Analyzes the founder's business context to deliver 3 best go-to-market strategies tailored to their current stage, product, and market. Asks up to 10 diagnostic questions when needed to understand product readiness,…

---
name: go-to-market-plan
description: Analyzes the founder's business context to deliver 3 best go-to-market strategies tailored to their current stage, product, and market. Asks up to 10 diagnostic questions when needed to understand product readiness, target market clarity, competitive positioning, and distribution channels. Use when user needs go-to-market strategy, launch planning, market entry strategy, or actionable GTM roadmap.
---

# 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 milesto

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ognjengt/founder-skills
git -C founder-skills checkout 90bc6f1424df

Works in

1. 2026-10-23
   ✓SAFE B 89 / 100

   first audit · source 90bc6f1424df

Questions about go-to-market-plan

• github.com/ognjengt/founder-skills/tree/main/skills/go-to-market — the audited source at commit 90bc6f1424df and every finding aboveObserved · 23 Oct 2026

Spotted something wrong? Report a correction · Methodology