Guides go-to-market (GTM) strategy—the blueprint for launching or repositioning a product that aligns product, marketing, sales, and customer success around reaching and winning target customers. Organizations with documented GTM see ~10% higher success rates and 3× revenue growth; ~72% of B2B miss GTM targets in year 1, often due to execution gaps. Use this skill when planning GTM for product launch, new market entry, repositioning, or feature launch.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongtm-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches gtm-strategy from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gtm-strategy. Access via /gtm-strategy in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides go-to-market (GTM) strategy—the blueprint for launching or repositioning a product that aligns product, marketing, sales, and customer success around reaching and winning target customers. Organizations with documented GTM see ~10% higher success rates and 3× revenue growth; ~72% of B2B miss GTM targets in year 1, often due to execution gaps. Use this skill when planning GTM for product launch, new market entry, repositioning, or feature launch.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Scenario | Scope | Use |
|---|---|---|
| Product launch | New product to market | Full GTM; see product-launch for launch execution |
| New market entry | New geography or segment | Full GTM; different buying behaviors, competitors, regulations |
| Repositioning | Shift who you serve, what you solve | Messaging, ICP, channel alignment; not just rebrand |
| Feature launch | New capability in existing product | Tiered by impact; T1 (revenue) = full planning; T2/T3 = lighter |
GTM vs product launch: GTM is the strategy; product launch is the execution phase. GTM applies to multiple scenarios—not just new products.
| Mode | When to Use | ACV | Buyer |
|---|---|---|---|
| Product-led (PLG) | Value in minutes; self-evaluate; simple adoption | <$10K | Buyer = end user |
| Sales-led (SLG) | Multi-stakeholder; complex procurement; implementation | >$25K | Enterprise; negotiation |
| Marketing-led (MLG) | Content, SEO, paid drive awareness; market education | Varies | Demand gen focus |
| Hybrid | PLG for acquisition; sales for expansion | Common | Self-serve → sales handoff |
Decision factors: ACV, product complexity, buyer profile, how customers want to buy. Target LTV:CAC ≥3:1; CAC payback <12 months.
| Phase | Weeks | Focus |
|---|---|---|
| Market analysis | 1–3 | Validate demand; competitive landscape; TAM; buying signals |
| Strategy design | 4–6 | ICP, personas; positioning; pricing; GTM mode; channels |
| Execution build | 7–9 | Messaging, content, sales playbook; tech stack |
| Launch & iterate | 10–12 | Go live; measure; iterate |
Key: Connect plan to real buying activity within 90 days—not disconnected strategy documents.
| Type | Level | Defines |
|---|---|---|
| ICP | Company | Which organizations deliver best unit economics; firmographics (industry, size, revenue), technographics, problem intensity |
| Buyer persona | Individual | Decision-makers within target companies; roles, goals, pain points, objections, preferred channels |
ICP impact: Defined ICPs → ~68% higher conversion, ~50% lower CAC, ~30% shorter sales cycles. Include negative profiles (explicit disqualifiers) to protect pipeline quality.
| Element | Purpose |
|---|---|
| TAM | Total addressable market; named account lists; primary TAM, serviceable TAM, accounts with buying signals |
| Competitive landscape | Customer bases, strengths, weaknesses, positioning claims |
| Buying patterns | Replace assumptions with data; customer pain points; decision criteria |
| Challenge | Mitigation |
|---|---|
| Customization | Product modularity; professional services; clear scope |
| Data security / private deployment | On-prem or private cloud; compliance; security certifications |
| Procurement cycles | Multi-stakeholder alignment; champion building; long sales cycles |
| Buy vs SaaS | Total cost of ownership; flexibility; ongoing value |
Use: When GTM targets enterprise or high-ACV—expect longer cycles, procurement, and security requirements.
~70% of international market entries fail within two years—often from overestimating demand, underestimating execution, spreading resources thin.
| Entry model | Trade-off |
|---|---|
| Organic expansion | High control; slower; capital-intensive |
| Strategic partnerships | Faster access; shared risk; reduced control |
| M&A / Acquisition | Immediate presence; high integration risk |
| Asset-light (EOR, outsourcing) | Fastest; minimal upfront; market testing |
| Pilot testing | Lowest commitment; validation |
Critical: Domestic playbook won't transfer. Buying behaviors vary (self-service US vs consultation-heavy Europe vs relationship-driven APAC); competitive landscapes shift; regulatory complexity multiplies (GDPR, data localization).
Repositioning = Strategic shift in who you serve, what problem you solve, where you play. Rebranding = Visual/verbal expression (logo, voice). Repositioning ≠ rebrand.
| When to reposition | Avoid |
|---|---|
| Moving upmarket (SMB → enterprise) | Quick fix for missed quarters |
| New geography with different dynamics | Leadership boredom |
| ICP fundamentally changed | |
| Major pivot, launch, or acquisition |
Success factors: Research-driven (customer discovery, market analysis); cross-functional alignment (sales, marketing, product, clinical); sharp differentiation.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
gtm-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
gtm-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added gtm-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added gtm-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: gtm-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: gtm-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added gtm-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
gtm-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
gtm-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
gtm-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 58