go-to-market-strategy
Skill54 starsChanged 31 days agoMITView on GitHub
Determine how to serve and win an accepted market over time. Use for GTM model, sales-led versus product-led versus partner-led or hybrid, route to market, motion priorities, responsibilities, validation and GTM strategy review. Market selection, prices, launches and final assets retain separate owners.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- varunk130/claude-code-skillstheir own version, first seen Oct 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- varunk130/claude-code-skills★ 1same 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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- account-based-marketingSkill
- acquisition-conversionSkill
- ad-creativeSkill
- analytics-trackingSkill
- aso-auditSkill
- buyer-resourcesSkill
- cold-emailSkill
- community-marketingSkill
- competitor-alternativesSkill
- competitor-profilingSkill
- content-strategySkill
- customer-marketingSkill
- customer-researchSkill
- email-sequenceSkill
- eventsSkill
- icp-and-buyer-personasSkill
- launch-readiness-checkSkill
- launch-strategySkill
- localization-claimsSkill
- market-entry-briefSkill
- market-entry-orchestrationSkill
- marketing-copySkill
- marketing-experimentationSkill
- market-intelligenceSkill
- messaging-consistency-auditSkill
- messaging-frameworkSkill
- objection-intelligenceSkill
- output-quality-checkSkill
- paid-adsSkill
- partner-marketingSkill
- positioning-strategySkill
- pricing-strategySkill
- product-activationSkill
- product-communicationsSkill
- product-marketing-contextSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- search-discoverabilitySkill
- social-contentSkill
- ssot-context-loopSkill
- upgrade-conversionSkill
- website-buyer-journeySkill
- win-loss-intelligenceSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.
- Very specific: line 14
Read ../_shared/segment-selection.md when an audience decision is needed.
- Distinctive: line 16
Treat the beachhead as a segment plus business use case, and consume a comparative opportunity decision before building the GTM route.
- Very specific: line 20
Do not edit SSOT. Route proposed canon changes to ssot-context-loop for human review and approval.
- Distinctive: line 26
When an accepted input is absent, name the upstream owner and gap.
- Very specific: line 65
Only after objective, accepted audience, strategy and constraints are established, consult ../_shared/tactic-library/guidance.md for …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Strategy
Approved context and evidence
Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.
Load only relevant approved manifest context and record sources in Inputs and assumptions.
Read ../_shared/segment-selection.md when an audience decision is needed; inherit accepted segments and ICP.
- For broad expansion or repositioning work, read
../_shared/opportunity-discovery.md. Treat the beachhead as a segment plus business use case, and consume a comparative opportunity decision before building the GTM route. A narrow, product-specific GTM request stays within its named scope. Separate sources, interpretation, and proposals. Missing evidence remains Assumed or Gap. Do not edit SSOT. Route proposed canon changes tossot-context-loopfor human review and approval.
Inputs and entry gate
Inventory accepted market decision (market-entry-brief), ICP/personas (icp-and-buyer-personas), positioning (positioning-strategy), messaging (messaging-framework), pricing/packaging (pricing-strategy) and relevant approved SSOT.
Consume applicable customer-research/VoC, competitor-profiling, win-loss-intelligence and objection-intelligence findings with provenance, sample limits and confidence. Intelligence owners collect and synthesize; this skill decides proposed commercial implications.
When an accepted input is absent, name the upstream owner and gap. A provisional option comparison is allowed with labeled assumptions; no invented accepted strategy or automatic canon replacement.
For broad expansion, propose the beachhead as an accepted segment plus a
specific business use case. Do not treat a trigger, infrastructure requirement,
or product feature as the use case, and do not select a new product without the
comparative opportunity decision described in ../_shared/opportunity-discovery.md.
Workflow
- Frame the commercial decision. State horizon, accepted market and buyer, buying committee, purchase complexity, value realization, contract/economic context and company constraints. Preserve accepted inputs verbatim in an inheritance register.
- Compare viable GTM models. Evaluate sales-led, product-led, partner-led and hybrid against buyer buying behavior, product time-to-value, adoption friction, service/support needs, deal economics, sales capacity, partner value and evidence. Separate observed facts from modeled assumptions. Hybrid needs explicit segment/stage responsibilities, not a list of every channel.
- Propose route and priorities. Explain the chosen model and rejected alternatives. Define direct/indirect route, motion/channel priorities, eligibility, commercial constraints and where each motion hands off. Pricing remains with
pricing-strategy; market selection stays withmarket-entry-brief. - Sequence and assign. Stage motions by evidence, dependencies and capacity. Specify PMM, Sales, Product, CS, Partners, Marketing, RevOps and Finance responsibilities, decision rights and owners. Do not equate a launch date with the ongoing GTM model.
- Validate and revisit. Define testable commercial assumptions, baseline/gaps, decision thresholds with rationale, guardrails, owners and milestones. Set a strategy review cadence and triggers such as buying-behavior change, economics deterioration, activation barriers, partner dependency or evidence contradicting canon. Avoid invented certainty and benchmarks.
- Route briefs. Hand objectives, accepted audience, approved message/proof, motion role, dependencies, budget assumptions, success measures and learning needs to execution owners. Produce no final channel assets here.
Handoffs
Carry the persona source and intelligence supporting motion choices into execution briefs, preserving evidence and approval status.
- Release-specific execution:
launch-strategy; accepted new-market orchestration:market-entry-orchestration. - Account, event, partner, post-sale or product narrative programs:
account-based-marketing,events,partner-marketing,customer-marketing,product-communications. - Seller, content and paid programs:
sales-enablement,content-strategy,paid-ads. - Activation and free/trial-to-paid:
product-activation,upgrade-conversion. - Measurement and commercial handoffs:
analytics-tracking,revops; commercial assumptions/prices:pricing-strategy.
Conflict and approval
If evidence challenges accepted market, ICP, positioning, messaging, pricing or GTM strategy, show the exact conflict, impact and source limitations. Propose review through ssot-context-loop and the upstream decision owner. Do not choose newer evidence silently, change canonical files, set prices independently or produce execution against an unapproved strategic change.
An accepted strategy may continue while review is pending only within its existing approvals and restrictions; flag affected plans and decision dependencies. Human approval is required before canonical strategic changes.
Required output
Inputs and assumptions; accepted-input inheritance register; decision/horizon; evidence and gaps; model/options comparison; recommended route and prioritized motions; commercial assumptions/constraints; sequencing; cross-functional responsibilities; validation plan; review cadence/reconsideration triggers; execution briefs/handoffs; canon conflicts/proposed reviews; ranked Evidence gaps.
output-quality-check checks this decision artifact against these requirements. Market-facing assets undergo messaging-consistency-audit; launch readiness remains independent.
Optional ideation
Only after objective, accepted audience, strategy and constraints are established, consult ../_shared/tactic-library/guidance.md for candidate tactics. The owning motion skill evaluates each candidate.
Related skills
market-entry-brief, icp-and-buyer-personas, positioning-strategy, messaging-framework, pricing-strategy, customer-research, competitor-profiling, win-loss-intelligence, objection-intelligence, launch-strategy, market-entry-orchestration, account-based-marketing, events, partner-marketing, customer-marketing, product-communications, sales-enablement, content-strategy, paid-ads, product-activation, upgrade-conversion, analytics-tracking, revops, ssot-context-loop.
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.

