gtm

gtm is a command for Claude Code from lucasgaravelli/pm-skills-claude-code. It costs 0 tokens per session (4,331 once invoked), scanned A, a copy of gtm, MIT.

A go-to-market (GTM) plan for launching a product or feature. It covers how to reach the target audience, what to say, how to measure results, and when each launch activity happens.

In plain words
What is it for?
Use it for a new product or feature launch, entering a new market or location, repositioning a product, or planning a campaign.
Why use it?
It brings product, marketing, and sales work into one coordinated plan. This reduces uncertainty about launch channels, messaging, timing, budget, and what counts as success.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

Good fit Use it for a new product or feature launch, entering a new market or location, repositioning a product, or planning a campaign.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lucasgaravelli/pm-skills-claude-code/gtm
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.

Clone the repo
git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-code

Made for: Claude Code.

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 gtm

README.md
[![agentmods](https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/gtm/github.svg)](https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/gtm)
Your own site
<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/gtm"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/gtm/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 gtm

Your own site · 80×15
<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/gtm"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/gtm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,331 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.
Origin 100% copy Near-identical to another mod 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.00000 $0.04331
Opus 5 $0.00000 $0.02166
Sonnet 5 $0.00000 $0.00866
Haiku 4.5 $0.00000 $0.00433

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

Security

Grade A, and why

gtm 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 9d 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.

Origin

This is a copy

100% identical to gtm — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/gtm.md · 516 lines

How it starts

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

/gtm

O que essa skill faz

Cria estratégia de go-to-market (GTM) com 4 elementos: Canais (como chega), Mensagens (por que compra), Métricas (como rastreia), Timeline (quando lança).

Saída: Plano GTM de 2-4 páginas pronto para alinhamento entre product, marketing, sales.


Quando usar

  • Feature/produto novo vai lançar
  • Entrando em novo segmento ou geografia
  • Campanha de reposicionamento
  • Spike no interesse (fale com press, etc)

Input esperado

Mínimo:

  • Feature ou produto: O que está lançando
  • Audiência alvo: Quem é o usuário primário
  • Timeline: Quando lança?
  • Budget: Quanto pode gastar?

Opcional:

  • Dados de descoberta (qual problema resolve)
  • Competitive positioning
  • Marketing assets já prontos
  • Partnership opportunities

Processo

  1. Positioning — Como você se descreve em 1 frase?
  2. Channels — Onde alcança audiência (email, ads, events, partnerships)?
  3. Messages — O que você diz em cada canal?
  4. Timeline — Quando cada tática sai?
  5. Metrics — Como mede sucesso?
  6. Success — Que números significam "funcionou"?

Output

# Go-to-Market Plan: [Feature/Produto]

## 1. Positioning

### Elevator pitch (1 frase)
[Como você se descreve para alguém em 30 segundos]

### Extended positioning (1 parágrafo)
[Problema que resolve, quem é, por que é diferente]

### Target persona
- **Name**: [Persona]
- **Role**: [Job title]
- **Problem**: [Que dor resolve]
- **Why cares**: [O que ganha]

---

## 2. Channel Strategy

### Primary channels (Onde alcança a maioria)

#### Channel 1: [Email to existing users]
- **Audience**: [1000 existing customers, engaged]
- **Tactic**: Anunciar via in-app + email notification
- **Timing**: [Dia de launch]
- **Expected reach**: 40% open rate = 400 users
- **Expected conversion**: 20% try feature = 80 users

#### Channel 2: [Webinar / Live demo]
- **Audience**: [100-150 prospects + customers]
- **Tactic**: 1-hour live product demo + Q&A
- **Timing**: [1 semana após launch]
- **Expected reach**: 60 people registradas, 40 attend
- **Expected conversion**: 15% = 6 leads qualificados

#### Channel 3: [Blog post]
- **Audience**: [Organic search + social]
- **Tactic**: Long-form content: "How we solved X" (thought leadership)
- **Timing**: [Dia de launch ou dia anterior]
- **Expected reach**: 500-1000 views first month
- **Expected conversion**: 2-3% = 10-20 leads

### Secondary channels (Nice to have, if time)

#### Channel A: [Press outreach]
- **Tactic**: Email 20 journalists sobre launch
- **Timing**: [2 dias antes, embargo até launch]
- **Expected**: 1-2 articles = brand awareness

#### Channel B: [Partner co-marketing]
- **Tactic**: [Partner X] menciona launch nos seus canais
- **Timing**: [Same day]
- **Expected**: 1000 impressions

#### Channel C: [Paid ads]
- **Budget**: [$X/semana]
- **Platform**: [LinkedIn, Google Ads, Facebook]
- **Audience**: [Lookalike of existing customers]
- **Timeline**: [Post-launch, if early metrics good]

---

## 3. Messaging Framework

### Primary message (Use in ALL channels)
**[Um statement que resume o value]**

Example: "With Acme deal war rooms, your team stops losing complex deals to communication chaos."

### Secondary messages (Customize por channel)

#### For existing customers (Email)
- "You asked for better collaboration. Here it is."
- "Reduce deal cycle time by 50%"
- "Try it free for 30 days"

#### For prospects (Webinar + Blog)
- "See how [company type] wins consultative deals 3x faster"
- "Built by people who get your sales process"
- "Feature that [competitor] doesn't have"

#### For press (PR)
- "New CRM feature helps mid-market sales teams..."
- "Founded by [team background] to solve [problem]"
- "[Customer name] saw [X] improvement in [metric]"

### Visual identity
- **Color/theme**: [Se tiver]
- **Imagery**: [Screenshots, customer photos, data viz]
- **Tone**: [Casual, professional, technical, fun]

---

## 4. Detailed Timeline

### Week before (Preparation)
- **Mon**: Marketing assets ready (email templates, blog post, slides)
- **Tue-Wed**: Internal training (sales, support know what to say)
- **Thu**: Press outreach begins (journalists get early access)
- **Fri**: Final QA (feature works, docs are correct)

### Launch day
- **8am**: Feature goes live in production
- **9am**: Announcement email sent to existing users
- **9:30am**: Blog post published + social media posts
- **10am**: Webinar registration opens
- **Throughout day**: Monitor support tickets, respond to questions

### Week 1 post-launch
- **Day 2**: Webinar happens (live demo + Q&A)
- **Day 3-5**: Drive engagement (social follow-up, email campaign)
- **Day 5**: Analyze metrics (what's working, what's not)
- **Day 7**: Paid ads start (if metrics good)

### Week 2-4
- **Ongoing**: Support + success team onboarding customers
- **Weekly**: Metric reviews, adjust tactics if needed
- **Week 3**: Partner co-marketing (if partnership exists)
- **Week 4**: Paid ads ongoing, content seeding

---

## 5. Metrics & Success Criteria

### Awareness metrics
| Metric | Target | How measure |
|--------|--------|------------|
| Blog views | 500+ | Analytics |
| Email opens | 40%+ | Email platform |
| Webinar registrations | 100+ | Eventbrite |
| Press mentions | 2+ | Google Alerts |
| Social impressions | 5000+ | Social platform |

### Engagement metrics
| Metric | Target | How measure |
|--------|--------|------------|
| Feature adoption (existing users) | 20%+ in week 1 | Product analytics |
| Trial signups (prospects) | 50+ in month 1 | Signup form |
| Webinar attendance | 40%+ of registered | Live count |
| Click-through rate (email) | 15%+ | Email platform |

### Conversion metrics
| Metric | Target | How measure |
|--------|--------|------------|
| Trial → paid conversion | 15%+ | Billing system |
| Webinar → lead qualification | 10%+ | CRM |
| Press → inbound leads | 2-5 | CRM source tracking |

### Revenue metrics
| Metric | Target | How measure |
|--------|--------|------------|
| New ARR from launch | $[X]k | Billing |
| Existing customer uplift | $[Y]k | Billing (higher tier) |
| Payback period | < 6 months | Finance |

---

## 6. Success Scenarios

### Best case (Everything works)
- **25%+ of existing users try feature**
- **100+ prospects sign up for trial**
- **20%+ trial → conversion**
- **Result**: $50k new ARR in first month

### Base case (Expected)
- **15% of existing users try feature**
- **50 prospects sign up for trial**
- **12% trial → conversion**
- **Result**: $25k new ARR in first month

### Worst case (Below expectations)
- **5% adoption**
- **20 trials**
- **5% conversion**
- **Result**: $5k ARR, need to iterate on messaging/positioning

---

## 7. Go/No-go Decision

### Go-live decision criteria (day before launch)
- ✅ Feature is stable (no critical bugs)
- ✅ Marketing assets are complete
- ✅ Team is trained
- ✅ Support is ready
- ✅ Analytics tracking is in place

### If any red, consider delaying 1 week

---

## 8. Contingency Plans

### If adoption is low (5% vs 15% target)
- **Hypothesis**: Messaging doesn't resonate
- **Action**: Run survey with non-adopters
- **Tactic**: New email with different angle
- **Timeline**: Week 2 follow-up

### If press falls through
- **Backup**: Partner mentions instead
- **Backup**: Organic social (influencer outreach)
- **Cost**: $0 (already planned)

### If webinar low attendance
- **Action**: Record, post to YouTube + Twitter
- **Action**: Email recording to all registrants
- **Timeline**: Day after webinar

---

## Owner & Approval

| Role | Decision | Owner |
|------|----------|-------|
| Product | Feature go-live | [PM] |
| Marketing | Campaign assets | [Mktg Lead] |
| Sales | Message + training | [Sales Lead] |
| Support | FAQ + training | [Support Lead] |

**Launch approved by**: [CEO/Product Lead]
**Date**: [Date]
**Expected launch date**: [Date]

Read the full file on GitHub · 516 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. 9d ago First seen · 516 lines · 0 tokens per session scan A 67e6edeb5645

Subscribe to this mod's changes

gtm is a command published in the GitHub repository lucasgaravelli/pm-skills-claude-code (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,331 tokens. A static security scan graded it A with 0 findings. It is 100% identical to gtm, differing in 0 lines, and is treated as a copy.