go-to-market-plan

go-to-market-plan is a skill for Claude Code from ognjengt/founder-skills. It costs 80 tokens per session (4,772 once invoked), scanned A, original, MIT.

A planning skill that examines a business, its product, market, and current stage to suggest three ways to reach customers. Go-to-market means the plan for launching and selling a product.

In plain words
What is it for?
Use it to assess launch readiness, clarify positioning and target markets, and create tailored customer-acquisition strategies from business details or diagnostic questions.
Why use it?
It helps when a business does not yet know which customers to target, how ready its product is, or which sales and distribution route to choose.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: names the AskUserQuestion tool.

Part of the founder-skills plugin — 15 skills shipped together

not rated 302repo +11 3mo ago A scan Socket: passSnyk: passSkillSpector: pass 80 tokens original MIT

Good fit Use it to assess launch readiness, clarify positioning and target markets, and create tailored customer-acquisition strategies from business details or diagnostic questions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ognjengt/founder-skills/go-to-market-plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ognjengt/founder-skills --skill go-to-market-plan
Clone the repo
git clone --depth 1 https://github.com/ognjengt/founder-skills

Made for: Claude Code.

Or install founder-skills, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for go-to-market-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/ognjengt/founder-skills/go-to-market-plan/github.svg)](https://agentmods.dev/skills/ognjengt/founder-skills/go-to-market-plan)
Your own site
<a href="https://agentmods.dev/skills/ognjengt/founder-skills/go-to-market-plan"><img src="https://agentmods.dev/badge/skills/ognjengt/founder-skills/go-to-market-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for go-to-market-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/ognjengt/founder-skills/go-to-market-plan"><img src="https://agentmods.dev/badge/skills/ognjengt/founder-skills/go-to-market-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,772 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 15 Feb 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.04772
Opus 5 $0.00040 $0.02386
Sonnet 5 $0.00016 $0.00954
Haiku 4.5 $0.00008 $0.00477

Measured 12d ago against content hash 432aa9426b77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

go-to-market-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/go-to-market-plan/SKILL.md · 445 lines

How it starts

The opening of the file, as written. The whole thing — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

Read the full file on GitHub · 445 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 445 lines · 80 tokens per session scan A 432aa9426b77

Subscribe to this mod's changes

go-to-market-plan is a skill published in the GitHub repository ognjengt/founder-skills (302 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 4,772 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens