go-to-market-planner
Skill3 starsChanged 4 months agoMITView on GitHub
Produce a go-to-market plan: target segments, channels, launch phases, messaging, and success metrics. Use when launching a product, entering a new market, or planning a GTM strategy after positioning is defined.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- SkillMedev/gtm-launchtheir own version, first seen Oct 5, 2026
- SkillMedev/solo-founder-stacktheir own version, first seen Oct 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- SkillMedev/gtm-launch★ 1same name
- SkillMedev/solo-founder-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- agent-memory-designerSkill
- ai-cost-optimizerSkill
- ai-evaluation-builderSkill
- ai-latency-optimizerSkill
- ai-solution-architectSkill
- ai-workflow-builderSkill
- context-engineeringSkill
- human-in-the-loop-designerSkill
- multi-agent-plannerSkill
- prompt-engineerSkill
- prompt-optimizerSkill
- prompt-reviewerSkill
- adr-generatorSkill
- api-designerSkill
- architecture-reviewSkill
- component-diagram-builderSkill
- container-diagram-builderSkill
- data-flow-analyzerSkill
- integration-plannerSkill
- observability-plannerSkill
- scalability-advisorSkill
- solution-architectureSkill
- system-context-builderSkill
- experiment-designerSkill
- pricing-strategy-advisorSkill
- mcp-best-practicesSkill
- mcp-client-generatorSkill
- mcp-security-reviewSkill
- mcp-server-generatorSkill
- mcp-tool-generatorSkill
- acceptance-criteria-generatorSkill
- analytics-instrumentation-plannerSkill
- competitive-analysisSkill
- epic-generatorSkill
- feature-prioritizationSkill
- idea-validatorSkill
- north-star-metric-advisorSkill
- okr-builderSkill
- persona-generatorSkill
- prd-generatorSkill
- problem-statement-builderSkill
- product-discovery-assistantSkill
- product-vision-builderSkill
- sprint-plannerSkill
- story-mappingSkill
- user-story-generatorSkill
- value-proposition-designerSkill
- chunking-strategy-advisorSkill
- embedding-strategy-advisorSkill
- hybrid-search-advisorSkill
- knowledge-ingestion-plannerSkill
- rag-architecture-designerSkill
- retriever-optimizerSkill
- ai-governance-advisorSkill
- ai-threat-modelingSkill
- guardrails-builderSkill
- owasp-llm-reviewerSkill
- prompt-injection-detectorSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
If value proposition is missing, stop and request it — GTM without positioning produces generic campaigns.
- Distinctive: line 150
Start with 10–20 design partners before paid acquisition.
- Distinctive: line 152
Document what you will not do in launch (non-goals).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go-to-Market Planner
Purpose
Produce a go-to-market (GTM) plan: who to reach first, through which channels, in what sequence, with what message, and how to measure launch success.
Input: Product/PRD summary, value proposition, competitive context (optional), budget and timeline constraints
Output: GTM Plan with segment prioritization, channel mix, phased launch timeline, messaging pillars, and KPI dashboard
Examples: See examples.md for worked input/output.
Workflow
Step 1: Confirm launch readiness inputs
| Input | Required | Source skill |
| Target customer & problem | Yes | product/problem-statement-builder |
| Value proposition | Yes | product/value-proposition-designer |
| MVP scope | Yes | product/prd-generator or feature-prioritization |
| Competitive wedge | Recommended | product/competitive-analysis |
| Pricing direction | Recommended | growth/pricing-strategy-advisor |
If value proposition is missing, stop and request it — GTM without positioning produces generic campaigns.
Step 2: Define ICP and beachhead segment
| Field | Definition |
| ICP firmographics | Company size, industry, geography |
| Persona | Buyer vs user vs champion |
| Pain intensity | Must-have vs nice-to-have |
| Reachability | Can we find and contact them? |
| Willingness to pay | Budget owner identified? |
Rank 1–3 segments; pick one beachhead for launch (not everyone at once).
Step 3: Select GTM motion
| Motion | Use when | Primary channels |
| Product-led (PLG) | Low touch, self-serve, fast TTV | Product, content, community |
| Sales-led | High ACV, complex buy, enterprise | Outbound, demos, partners |
| Community-led | Developer tools, open core | Docs, Discord, advocates |
| Hybrid | Mid-market SaaS | PLG entry + sales assist |
State chosen motion and why alternatives were rejected.
Step 4: Build channel plan
Per channel document:
| Channel | Role in funnel | Owner | Budget | Leading indicator |
| Content/SEO | Awareness | Marketing | $ | Organic traffic |
| Paid | Acquisition | Growth | $ | CAC |
| Product virality | Activation | Product | — | Invite rate |
| Sales outbound | Conversion | Sales | $ | SQLs |
| Partnerships | Distribution | BD | — | Referral pipeline |
For AI products: add trust channels (demos, case studies, security page) — buyers need proof, not hype.
Step 5: Phased launch timeline
| Phase | Duration | Goal | Activities |
| Alpha | 2–4 wk | Learn | Design partners, qualitative feedback |
| Beta | 4–8 wk | Validate | Limited access, measure activation |
| GA | ongoing | Scale | Full channel mix, optimize CAC/LTV |
Each phase has entry criteria, exit criteria, and kill criteria if metrics fail.
Step 6: Messaging architecture
| Level | Content |
| One-liner | Problem + outcome |
| Elevator pitch | 30-second version for ICP |
| Pillars | 3 proof-backed themes (not feature lists) |
| Objection map | Top 5 objections + responses |
| AI disclosure | How you describe AI capabilities honestly |
Align with value proposition; do not invent new positioning here.
Step 7: Define launch KPIs
| Metric | Target | Measurement |
| Activation | e.g. 40% complete core action D7 | Product analytics |
| Pipeline | SQLs or signups/week | CRM / product |
| CAC (if paid) | < X% of LTV | Finance + ads |
| NPS / qualitative | Baseline score | Surveys |
Link events to product/analytics-instrumentation-planner or growth/experiment-designer.
Step 8: Validate
Run Validation checklist.
Decision Rules
| Condition | Action |
| No single beachhead segment | Stop; force rank — launch one segment first |
| B2B enterprise + PLG only budget | Flag mismatch; recommend sales assist or narrow ICP |
| Pre-product / no MVP | Limit to alpha design-partner plan only |
| Regulated industry | Add compliance review gate before public GA |
| AI product without eval metrics | Require quality KPI in launch dashboard |
| Launch date immovable | Cut channels, not measurement |
Validation
- Beachhead ICP defined with firmographics and persona
- GTM motion selected with rationale
- ≥3 channels with owners and leading indicators
- Phased timeline with entry/exit/kill criteria
- Messaging pillars tied to value proposition
- Launch KPIs with targets and data sources
- Dependencies on pricing and analytics documented
- Risks and mitigations listed (competitor response, budget)
Anti-patterns
- Spray and pray — every channel at once with no beachhead.
- Launch without activation metric — vanity traffic, no product signal.
- Feature launch, not outcome launch — messaging is a changelog.
- Ignoring sales cycle — enterprise GTM with self-serve assumptions.
- AI hype positioning — overpromising capabilities eval cannot support.
Best Practices
- Start with 10–20 design partners before paid acquisition.
- Pair qualitative interviews with funnel metrics each phase.
- Document what you will not do in launch (non-goals).
- Refresh competitive messaging quarterly in fast-moving AI categories.
- Hand off instrumentation before beta opens.
Output Structure
# GTM Plan: [Product Name]
## Launch context
[Motion, beachhead, timeline constraints]
## Beachhead ICP
[Segment definition and ranking]
## Channel plan
| Channel | Funnel stage | Owner | KPI |
|---------|--------------|-------|-----|
## Launch phases
### Alpha / Beta / GA
[Criteria and activities]
## Messaging
[Pillars, pitch, objections]
## KPIs
| Metric | Target | Source |
|--------|--------|--------|
## Risks
| Risk | Mitigation |
|------|------------|
## Dependencies
[Pricing, analytics, product readiness]Next Skills
| Outcome | Recommended Skill |
| Set price before launch | growth/pricing-strategy-advisor |
| Design launch experiments | growth/experiment-designer |
| Instrument funnels | product/analytics-instrumentation-planner |
| Refine positioning | product/value-proposition-designer |
| Competitive context | product/competitive-analysis |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

