Receber por email
← Voltar para o catálogo

ops-gtm

Go-to-market strategy planner. Generates a complete GTM plan across paid, unpaid, marketing, sales, and AI-automation channels for any project — and hands executable campaigns off to /marketing.

3.1kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add davepoon/buildwithclaude

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/ops-gtm/svg)](https://www.skillteca.com.br/skills/ops-gtm)
#ai

Skills relacionadas

Ver todas de Marketing →

Alerta por categoria

Receba novas skills de Marketing toda segunda

1 email curto, só com as skills novas de Marketing. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

OPS ► GTM COMMAND CENTER

Strategy layer that sits on top of /marketing. /marketing runs campaigns; /gtm decides what to run, across paid, unpaid, sales, and AI-automation channels, and then hands the executable pieces to /marketing via the Skill tool.

Runtime Context

Before executing, load available context:

  1. Preferences: Read ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json
  2. timezone — timestamp all output correctly
  3. gtm_default_project, gtm_default_audience, gtm_brand_voice — project-level defaults when set
  4. gtm_monthly_budget, gtm_stage (pre-launch|beta|ga|scale) — used to tune channel recommendations
  1. Cached plans: List ${CLAUDE_PLUGIN_DATA_DIR}/gtm/*.md to surface recent plans. Never overwrite a prior plan file — always append a new dated file.
  1. Daemon health: Read ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json. If action_needed is not null, surface it before running any long planning flow.
  1. Repo auto-scan (background): For the current working directory, in parallel and with run_in_background: true:
  2. git remote -v → infer project slug and org
  3. cat README.md (or README.*) → product description, ICP hints
  4. Glob package.json, pyproject.toml, Cargo.toml, go.mod → tech stack
  5. Glob .planning/**/*.md and docs/**/*.md → prior briefs, positioning notes
  6. Resolve: project name, one-line pitch, primary tech, existing channels hinted in the repo
  1. /marketing credential probe (read-only): Do NOT re-resolve API keys in this skill. Instead, when the user asks to launch something, delegate to /marketing via the Skill tool — /marketing owns the credential resolution chain (userConfig → env vars → Doppler → Dashlane → Keychain → gcloud ADC).

Agent Teams support

If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams for the plan sub-command so the four research agents share context and report progress in real-time:

TeamCreate("gtm-research-team")
Agent(team_name="gtm-research-team", name="paid-research",       prompt="Research paid acquisition channels that fit ${PROJECT_TYPE} at ${STAGE} with $${MONTHLY_BUDGET}/mo. Return a ranked list with fit signals, expected CAC, and which /marketing sub-command (if any) executes each channel.")
Agent(team_name="gtm-research-team", name="unpaid-research",     prompt="Research organic channels (SEO, content, community, PR, partnerships, referrals, lifecycle email) for ${PROJECT_TYPE} at ${STAGE}. Return ranked list with effort estimate, time-to-signal, and /marketing sub-command mapping.")
Agent(team_name="gtm-research-team", name="sales-research",      prompt="Design a sales motion for ${PROJECT_TYPE}: outbound vs inbound vs PLG vs channel. Propose a 30/60/90 plan with concrete activities and target metrics.")
Agent(team_name="gtm-research-team", name="automation-research", prompt="Propose AI-automation recipes: lead enrichment, personalized outreach, content ops, lifecycle copy, support deflection, lead scoring. For each, list trigger, model/tool stack, and where it plugs into /marketing.")

If the flag is NOT set, use standard fire-and-forget subagents with the same four prompts.

Sub-command Routing

Route $ARGUMENTS to the correct section below:

| Input | Action | |---|---| | (empty), plan | Full GTM plan across all four avenues | | paid | Paid acquisition deep-dive (Meta, Google, LinkedIn, TikTok, affiliates, sponsorships) | | unpaid | Organic deep-dive (SEO, content, community, PR, partnerships, referrals, lifecycle email) | | sales | Sales motion (outbound, inbound, PLG, channel / partner) | | automation | AI-automation playbook for GTM | | launch | 30/60/90 launch calendar + pre-flight checklist | | brief | One-page positioning brief (ICP, value prop, messaging pillars) | | setup | Configure default project, audience, budget tier, brand voice |

Arguments are free-form — treat /gtm plan for my-project $2k/mo pre-launch as equivalent to plan with intake values pre-filled.

Project Intake

Before producing any plan section, make sure the following are known. Source them in this order — only ask the user for what's still missing.

  1. Auto-scan the repo (step 4 of Runtime Context).
  2. Read prefs for gtm_default_* keys.
  3. Parse free-text in $ARGUMENTS for budget, stage, and project name.
  4. AskUserQuestion for gaps — respect Rule 1 (max 4 options per call; batch if needed).

Use these four questions in order, skipping any already known:

  • Project type — [B2B SaaS, B2C product, Marketplace, Dev tool / API]
  • Stage — [Pre-launch, Beta / early access, GA (live), Scale (growth)]
  • Primary goal (next 90 days) — [Awareness, Signups / leads, Revenue, Retention / expansion]
  • Monthly budget tier — [<$1k, $1k–5k, $5k–25k, $25k+]

If a Rule-1 batch overflows (e.g. more than 4 project types needed), paginate with [More options...] as the 4th slot.

Per Rule 3, never silently skip an intake question — if the user hits Escape, offer [Paste manually] / [Use default] / [Skip this only].

Channel / Avenue Catalog

This is the source-of-truth list the planner draws from. Each row: avenue → fit signals → cost profile → execution path. The execution path is what makes /gtm seamless with /marketing: if a /marketing sub-command exists for a channel, the plan recommends it by name; otherwise the channel is marked manual and the plan includes templated next-actions instead.

Paid

| Channel | Fits | Cost profile | Execution | |---|---|---|---| | Meta Ads (Facebook + Instagram) | B2C, marketplace, broad consumer | $5–50 CPA typical | /marketing ads · /marketing meta create-campaign | | Google Ads — Search | High-intent buyers, existing demand | $1–30 CPC | /marketing google-ads | | Google Ads — Performance Max | E-comm with catalog | Blended CPA | /marketing google-ads | | YouTube Ads | Awareness at scale | $0.01–0.30 CPV | /marketing google-ads (video campaigns) | | LinkedIn Ads | B2B, ACV > $10k | $8–15 CPC, $50+ CPL | manual — LinkedIn Campaign Manager | | TikTok Ads | B2C, < 35 audience, creative-led | $1–10 CPC | manual — TikTok Ads Manager | | Reddit / X / Pinterest | Niche communities | Varies | manual | | Podcast sponsorships | Trust-driven, narrow ICP | $20–50 CPM | manual — direct sponsor deals | | Affiliate / partner program | Marketplace, SaaS with referral loop | Rev-share | manual — Rewardful / PartnerStack |

Unpaid (Organic)

| Channel | Fits | Effort | Execution | |---|---|---|---| | Programmatic SEO | Dev tools, marketplaces, comparison queries | High upfront, compounding | /marketing seo (tracking) + manual content ops | | Topic-cluster SEO | Content-led SaaS, info-intent | Medium, 3–6mo to signal | /marketing seo | | Lifecycle email (welcome, nurture, winback) | Any with email capture | Medium, high leverage | /marketing email (Klaviyo flows) | | Instagram organic | Visual product, lifestyle | Medium, daily | /marketing instagram | | X / LinkedIn founder-led | B2B, dev tools, thought leadership | Daily, high-leverage | manual | | Community building (Discord / Slack / forum) | Dev tools, B2C with passion | High, ongoing | manual | | PR / launch pads (Product Hunt, HN, press) | Any at launch | Spiky | /gtm launch checklist + manual | | Partnerships / integrations | SaaS, marketplaces | Medium, compounding | manual | | Referral program | Any with product-led signup | Low eng cost, high leverage | manual — plug into lifecycle email |

Sales

| Motion | Fits | Execution | |---|---|---| | Outbound (cold email + LinkedIn) | B2B, ACV > $5k | /gtm automation (AI-personalized) + manual sending tool | | Inbound (demo form → AE) | B2B SaaS with pricing page | manual CRM + routing | | Product-Led Growth (self-serve) | Dev tools, horizontal SaaS | manual — instrument onboarding; /marketing email for lifecycle

Compartilhar X LinkedIn