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:
Preferences: Read ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json
timezone — timestamp all output correctly
gtm_default_project, gtm_default_audience, gtm_brand_voice — project-level defaults when set
gtm_monthly_budget, gtm_stage (pre-launch|beta|ga|scale) — used to tune channel recommendations
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.
Daemon health: Read ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json. If action_needed is not null, surface it before running any long planning flow.
Repo auto-scan (background): For the current working directory, in parallel and with run_in_background: true:
git remote -v → infer project slug and org
cat README.md (or README.*) → product description, ICP hints
- Glob
package.json, pyproject.toml, Cargo.toml, go.mod → tech stack
- Glob
.planning/**/*.md and docs/**/*.md → prior briefs, positioning notes
- Resolve: project name, one-line pitch, primary tech, existing channels hinted in the repo
/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.
- Auto-scan the repo (step 4 of Runtime Context).
- Read prefs for
gtm_default_* keys.
- Parse free-text in
$ARGUMENTS for budget, stage, and project name.
- 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 |
| Channel / partner |
Enterprise, vertical SaaS |
manual — co-selling motion |
AI Automation
| Recipe |
What it does |
Stack |
Plugs into |
| AI cold-email personalization |
LLM generates opener from enrichment data |
Clay / Apollo + Claude |
outbound sales |
| Generative SEO clusters |
LLM drafts topic-cluster outlines from seed keywords |
Claude + GSC data |
/marketing seo |
| Lifecycle copy generator |
Auto-draft Klaviyo flow emails per segment |
Claude + Klaviyo data |
/marketing email |
| Ad creative variants |
Bulk-generate Meta/Google ad copy A/B sets |
Claude + /marketing ads insights |
/marketing meta create-campaign · /marketing google-ads |
| Support deflection |
LLM answers tier-1 tickets from docs |
Claude + help-center KB |
manual — help desk |
| Lead scoring |
LLM scores inbound leads on ICP fit |
Claude + CRM data |
manual — CRM |
| Content repurposing |
Long-form → tweets, LinkedIn posts, newsletter |
Claude |
/marketing instagram · manual social |
plan — full GTM plan (default)
Intake per Project Intake section.
Spawn the four research agents (Agent Teams if flag set, else fire-and-forget).
Assemble the plan in this order:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GTM PLAN — [project] ([stage], [goal], $[budget]/mo)
[timestamp]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
POSITIONING
ICP: [one sentence]
Value prop: [one sentence]
Messaging: [3 pillars, comma-separated]
PAID (next 30 days)
1. [Channel] $[X]/mo Expected CAC: $[X] Execute: /marketing ads
2. [Channel] $[X]/mo Expected CAC: $[X] Execute: manual
UNPAID (next 90 days)
1. [Channel] Effort: [L/M/H] Signal in: [X wks] Execute: /marketing seo
2. [Channel] ...
SALES
Motion: [Outbound / Inbound / PLG / Channel]
30/60/90: [one line summary]
AUTOMATION (AI-powered)
1. [Recipe] Plugs into: /marketing email
2. [Recipe] Plugs into: outbound
KPIs
North star: [metric + target]
Leading: [3 leading indicators]
BUDGET ROLLUP
Paid: $[X]/mo
Tools/SaaS: $[X]/mo
Total: $[X]/mo
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Persist the plan to ${CLAUDE_PLUGIN_DATA_DIR}/gtm/<project-slug>-$(date +%Y-%m-%d).md (create the directory if missing). Never overwrite — if the file exists, append -v2, -v3.
Handoff prompt — end with an AskUserQuestion (≤4 options per Rule 1):
[Launch via /marketing] — hand top executable items to /marketing
[Save only] — keep the plan file, take no action
[Refine plan] — re-run with adjusted intake
[Schedule follow-up] — revisit in 7/30 days (delegate to /ops cron if available)
On [Launch via /marketing], iterate through plan items whose execution path starts with /marketing and invoke them one at a time via the Skill tool:
Skill("ops-marketing", args="campaigns")
Skill("ops-marketing", args="ads")
Skill("ops-marketing", args="email")
Never silently skip an item (Rule 3) — for each, ask [Launch, Skip, Edit first].
Per Rule 5, do NOT auto-launch anything that spends money or sends to real recipients without explicit per-item confirmation. The plan recommends; /marketing executes; the user approves each paid or outbound action.
paid — paid acquisition deep-dive
Same intake, but only spawn the paid-research agent. Render just the PAID block, with up to 5 channel rows and for each:
- Expected CAC range (cite source or reasoning)
- Creative angle suggestion
- Starting budget
- Attribution setup note (how
/marketing attribution will measure it)
Execute: line pointing to the /marketing sub-command or manual
End with the same handoff prompt as plan, scoped to paid channels.
unpaid — organic deep-dive
Spawn unpaid-research only. For each recommended channel output:
- Why it fits (fit signals from intake)
- First-30-days concrete actions (3 bullets)
- Time-to-signal
- Measurement: which
/marketing sub-command tracks it (/marketing seo, /marketing email, /marketing instagram) or manual + tool
- Lifecycle email is first-class here — recommend specific Klaviyo flows and note that
/marketing email can scaffold them
sales — sales motion
Spawn sales-research only. Produce:
- Motion pick with one-paragraph rationale (Outbound / Inbound / PLG / Channel — Rule 1: these are the exact 4 options if you need the user to choose).
- ICP slice — which segment to hit first, sized from intake.
- 30/60/90 plan — week-by-week activities (e.g. week 1: build list of 500 accounts; week 2: 200 outbound opens; …).
- Tooling — CRM, enrichment, sequencer; note when AI automation from the automation section fits.
- Handoff — offer
[Automate outreach via /gtm automation, Skip, Edit motion].
automation — AI automation playbook
Spawn automation-research only. Render each recipe with:
- Trigger condition (what event fires it)
- Model / tool stack (default to Claude + the ops tool listed in the catalog)
- Integration point — specifically, which
/marketing sub-command or external system it reads from and writes to
- Risk flags (PII, cost, brand-voice drift) and the guardrails that mitigate them
- Starter prompt / pseudo-code snippet so the user can copy-paste
End with AskUserQuestion offering [Scaffold recipe now, Save only, Pick different recipe].
launch — 30/60/90 launch calendar
Used at stage = pre-launch or beta. Produces a week-by-week calendar of launch activities across all four avenues.
Required pre-flight checklist (render and check what's ready vs open):
☐ Positioning brief → /gtm brief
☐ Landing page live → manual
☐ Analytics wired → /marketing setup (GA4 + GSC)
☐ Email capture live → /marketing email (Klaviyo list)
☐ Ad accounts ready → /marketing setup (Meta, Google)
☐ Social handles claimed → manual
☐ Product Hunt / HN plan → this skill, below
☐ Press / creator list → manual
Launch-day playbook: render hourly timeline for T-7d through T+14d, with concrete actions and the /marketing command (or manual step) for each.
brief — one-page positioning brief
Fast path — does NOT spawn the four research agents. Just intake + a single call to write the brief. Fields: ICP, Pain, Value prop, 3 messaging pillars, Proof points, Anti-positioning (who it's NOT for). Save to ${CLAUDE_PLUGIN_DATA_DIR}/gtm/<project-slug>-brief-$(date +%Y-%m-%d).md.
This is the cheapest entry point — recommend running /gtm brief before /gtm plan when the project's positioning isn't already written down.
setup
Configure GTM defaults so subsequent runs skip the intake questions. Per Rule 4, run every Bash call with run_in_background: true unless the result is needed for the very next decision.
Auto-scan (background) first:
# Existing prefs
jq -r '{project: .gtm_default_project, audience: .gtm_default_audience, voice: .gtm_brand_voice, budget: .gtm_monthly_budget, stage: .gtm_stage}' "$PREFS_PATH" 2>/dev/null
# Repo signals
git -C "$PWD" remote get-url origin 2>/dev/null
head -50 README.md 2>/dev/null
ls .planning/ 2>/dev/null
Then prompt for what's missing (≤4 options per Rule 1), in this order:
- Default project name — free-text, pre-filled from git remote slug
- Project type —
[B2B SaaS, B2C product, Marketplace, Dev tool / API]
- Stage —
[Pre-launch, Beta, GA, Scale]
- Monthly budget tier —
[<$1k, $1k–5k, $5k–25k, $25k+]
- Brand voice —
[Playful, Professional, Technical, Bold]
Save to $PREFS_PATH as gtm_default_project, gtm_project_type, gtm_stage, gtm_monthly_budget, gtm_brand_voice. Never write API keys here — GTM does not own any credentials (/marketing does).
Finish with a smoke test: run /gtm brief in background and report ✓ setup complete — try /gtm plan or ✗ [error].
Plugin Rules compliance (required reading)
All behavior above respects claude-ops/CLAUDE.md:
- Rule 0 — public repo: every example above uses
your-project, you@example.com, <YOUR_TOKEN>. Never save user-specific data outside $PREFS_PATH or ${CLAUDE_PLUGIN_DATA_DIR}/gtm/.
- Rule 1 — ≤4 options per AskUserQuestion: every prompt in this file lists exactly ≤4. Paginate with
[More options...] if a dynamic list grows past 4.
- Rule 3 — never auto-skip: on launch handoff, every plan item gets an explicit
[Launch, Skip, Edit first] prompt. No silent skipping.
- Rule 4 — background by default during setup: all Bash calls in the
setup flow use run_in_background: true.
- Rule 5 — destructive actions need explicit confirmation:
/gtm never spends money or sends messages directly — it delegates to /marketing, which owns per-action confirmation. Recommendations are just that.
Why this skill is thin
/gtm deliberately does NOT re-implement channel APIs. Credential resolution, curl calls, daemon data, and dashboards all live in /marketing. This skill is a strategy-and-handoff layer. If a capability belongs to a channel API, add it to /marketing; if it belongs to planning, it goes here.
Source: davepoon/buildwithclaude → plugins/claude-ops/skills/ops-gtm/SKILL.md
1---
2name: ops-gtm
3description: "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."
4allowed-tools: "Bash Read Write Grep Glob Agent TeamCreate SendMessage AskUserQuestion WebFetch WebSearch Skill"
5category: marketing-and-growth
6source_repo: davepoon/buildwithclaude
7source_path: "plugins/claude-ops/skills/ops-gtm/SKILL.md"
8source_url: https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/claude-ops/skills/ops-gtm/SKILL.md
9metadata:
10 source: https://skillmd.com/skills/davepoon/ops-gtm
11---
12
13
14# OPS ► GTM COMMAND CENTER
15
16Strategy 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.
17
18## Runtime Context
19
20Before executing, load available context:
21
221. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json`
23 - `timezone` — timestamp all output correctly
24 - `gtm_default_project`, `gtm_default_audience`, `gtm_brand_voice` — project-level defaults when set
25 - `gtm_monthly_budget`, `gtm_stage` (`pre-launch|beta|ga|scale`) — used to tune channel recommendations
26
272. **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.
28
293. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json`. If `action_needed` is not null, surface it before running any long planning flow.
30
314. **Repo auto-scan (background)**: For the current working directory, in parallel and with `run_in_background: true`:
32 - `git remote -v` → infer project slug and org
33 - `cat README.md` (or `README.*`) → product description, ICP hints
34 - Glob `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod` → tech stack
35 - Glob `.planning/**/*.md` and `docs/**/*.md` → prior briefs, positioning notes
36 - Resolve: project name, one-line pitch, primary tech, existing channels hinted in the repo
37
385. **`/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).
39
40## Agent Teams support
41
42If `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:
43
44```
45TeamCreate("gtm-research-team")
46Agent(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.")
47Agent(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.")
48Agent(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.")
49Agent(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.")
50```
51
52If the flag is NOT set, use standard fire-and-forget subagents with the same four prompts.
53
54---
55
56## Sub-command Routing
57
58Route `$ARGUMENTS` to the correct section below:
59
60| Input | Action |
61|---|---|
62| (empty), plan | Full GTM plan across all four avenues |
63| paid | Paid acquisition deep-dive (Meta, Google, LinkedIn, TikTok, affiliates, sponsorships) |
64| unpaid | Organic deep-dive (SEO, content, community, PR, partnerships, referrals, lifecycle email) |
65| sales | Sales motion (outbound, inbound, PLG, channel / partner) |
66| automation | AI-automation playbook for GTM |
67| launch | 30/60/90 launch calendar + pre-flight checklist |
68| brief | One-page positioning brief (ICP, value prop, messaging pillars) |
69| setup | Configure default project, audience, budget tier, brand voice |
70
71Arguments are free-form — treat `/gtm plan for my-project $2k/mo pre-launch` as equivalent to `plan` with intake values pre-filled.
72
73---
74
75## Project Intake
76
77Before producing any plan section, make sure the following are known. Source them in this order — only ask the user for what's still missing.
78
791. **Auto-scan the repo** (step 4 of Runtime Context).
802. **Read prefs** for `gtm_default_*` keys.
813. **Parse free-text in `$ARGUMENTS`** for budget, stage, and project name.
824. **AskUserQuestion for gaps** — respect Rule 1 (max 4 options per call; batch if needed).
83
84Use these four questions in order, skipping any already known:
85
86- **Project type** — `[B2B SaaS, B2C product, Marketplace, Dev tool / API]`
87- **Stage** — `[Pre-launch, Beta / early access, GA (live), Scale (growth)]`
88- **Primary goal (next 90 days)** — `[Awareness, Signups / leads, Revenue, Retention / expansion]`
89- **Monthly budget tier** — `[<$1k, $1k–5k, $5k–25k, $25k+]`
90
91If a Rule-1 batch overflows (e.g. more than 4 project types needed), paginate with `[More options...]` as the 4th slot.
92
93Per Rule 3, never silently skip an intake question — if the user hits Escape, offer `[Paste manually]` / `[Use default]` / `[Skip this only]`.
94
95---
96
97## Channel / Avenue Catalog
98
99This 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.
100
101### Paid
102
103| Channel | Fits | Cost profile | Execution |
104|---|---|---|---|
105| Meta Ads (Facebook + Instagram) | B2C, marketplace, broad consumer | $5–50 CPA typical | `/marketing ads` · `/marketing meta create-campaign` |
106| Google Ads — Search | High-intent buyers, existing demand | $1–30 CPC | `/marketing google-ads` |
107| Google Ads — Performance Max | E-comm with catalog | Blended CPA | `/marketing google-ads` |
108| YouTube Ads | Awareness at scale | $0.01–0.30 CPV | `/marketing google-ads` (video campaigns) |
109| LinkedIn Ads | B2B, ACV > $10k | $8–15 CPC, $50+ CPL | manual — LinkedIn Campaign Manager |
110| TikTok Ads | B2C, < 35 audience, creative-led | $1–10 CPC | manual — TikTok Ads Manager |
111| Reddit / X / Pinterest | Niche communities | Varies | manual |
112| Podcast sponsorships | Trust-driven, narrow ICP | $20–50 CPM | manual — direct sponsor deals |
113| Affiliate / partner program | Marketplace, SaaS with referral loop | Rev-share | manual — Rewardful / PartnerStack |
114
115### Unpaid (Organic)
116
117| Channel | Fits | Effort | Execution |
118|---|---|---|---|
119| Programmatic SEO | Dev tools, marketplaces, comparison queries | High upfront, compounding | `/marketing seo` (tracking) + manual content ops |
120| Topic-cluster SEO | Content-led SaaS, info-intent | Medium, 3–6mo to signal | `/marketing seo` |
121| Lifecycle email (welcome, nurture, winback) | Any with email capture | Medium, high leverage | `/marketing email` (Klaviyo flows) |
122| Instagram organic | Visual product, lifestyle | Medium, daily | `/marketing instagram` |
123| X / LinkedIn founder-led | B2B, dev tools, thought leadership | Daily, high-leverage | manual |
124| Community building (Discord / Slack / forum) | Dev tools, B2C with passion | High, ongoing | manual |
125| PR / launch pads (Product Hunt, HN, press) | Any at launch | Spiky | `/gtm launch` checklist + manual |
126| Partnerships / integrations | SaaS, marketplaces | Medium, compounding | manual |
127| Referral program | Any with product-led signup | Low eng cost, high leverage | manual — plug into lifecycle email |
128
129### Sales
130
131| Motion | Fits | Execution |
132|---|---|---|
133| Outbound (cold email + LinkedIn) | B2B, ACV > $5k | `/gtm automation` (AI-personalized) + manual sending tool |
134| Inbound (demo form → AE) | B2B SaaS with pricing page | manual CRM + routing |
135| Product-Led Growth (self-serve) | Dev tools, horizontal SaaS | manual — instrument onboarding; `/marketing email` for lifecycle |
136| Channel / partner | Enterprise, vertical SaaS | manual — co-selling motion |
137
138### AI Automation
139
140| Recipe | What it does | Stack | Plugs into |
141|---|---|---|---|
142| AI cold-email personalization | LLM generates opener from enrichment data | Clay / Apollo + Claude | outbound sales |
143| Generative SEO clusters | LLM drafts topic-cluster outlines from seed keywords | Claude + GSC data | `/marketing seo` |
144| Lifecycle copy generator | Auto-draft Klaviyo flow emails per segment | Claude + Klaviyo data | `/marketing email` |
145| Ad creative variants | Bulk-generate Meta/Google ad copy A/B sets | Claude + `/marketing ads` insights | `/marketing meta create-campaign` · `/marketing google-ads` |
146| Support deflection | LLM answers tier-1 tickets from docs | Claude + help-center KB | manual — help desk |
147| Lead scoring | LLM scores inbound leads on ICP fit | Claude + CRM data | manual — CRM |
148| Content repurposing | Long-form → tweets, LinkedIn posts, newsletter | Claude | `/marketing instagram` · manual social |
149
150---
151
152## plan — full GTM plan (default)
153
1541. **Intake** per Project Intake section.
1552. **Spawn the four research agents** (Agent Teams if flag set, else fire-and-forget).
1563. **Assemble the plan** in this order:
157
158 ```
159 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
160 GTM PLAN — [project] ([stage], [goal], $[budget]/mo)
161 [timestamp]
162 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
163 POSITIONING
164 ICP: [one sentence]
165 Value prop: [one sentence]
166 Messaging: [3 pillars, comma-separated]
167
168 PAID (next 30 days)
169 1. [Channel] $[X]/mo Expected CAC: $[X] Execute: /marketing ads
170 2. [Channel] $[X]/mo Expected CAC: $[X] Execute: manual
171
172 UNPAID (next 90 days)
173 1. [Channel] Effort: [L/M/H] Signal in: [X wks] Execute: /marketing seo
174 2. [Channel] ...
175
176 SALES
177 Motion: [Outbound / Inbound / PLG / Channel]
178 30/60/90: [one line summary]
179
180 AUTOMATION (AI-powered)
181 1. [Recipe] Plugs into: /marketing email
182 2. [Recipe] Plugs into: outbound
183
184 KPIs
185 North star: [metric + target]
186 Leading: [3 leading indicators]
187
188 BUDGET ROLLUP
189 Paid: $[X]/mo
190 Tools/SaaS: $[X]/mo
191 Total: $[X]/mo
192 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
193 ```
194
1954. **Persist the plan** to `${CLAUDE_PLUGIN_DATA_DIR}/gtm/<project-slug>-$(date +%Y-%m-%d).md` (create the directory if missing). Never overwrite — if the file exists, append `-v2`, `-v3`.
1965. **Handoff prompt** — end with an `AskUserQuestion` (≤4 options per Rule 1):
197 - `[Launch via /marketing]` — hand top executable items to `/marketing`
198 - `[Save only]` — keep the plan file, take no action
199 - `[Refine plan]` — re-run with adjusted intake
200 - `[Schedule follow-up]` — revisit in 7/30 days (delegate to `/ops cron` if available)
201
202On `[Launch via /marketing]`, iterate through plan items whose execution path starts with `/marketing` and invoke them one at a time via the Skill tool:
203
204```
205Skill("ops-marketing", args="campaigns")
206Skill("ops-marketing", args="ads")
207Skill("ops-marketing", args="email")
208```
209
210Never silently skip an item (Rule 3) — for each, ask `[Launch, Skip, Edit first]`.
211
212Per Rule 5, do NOT auto-launch anything that spends money or sends to real recipients without explicit per-item confirmation. The plan recommends; `/marketing` executes; the user approves each paid or outbound action.
213
214---
215
216## paid — paid acquisition deep-dive
217
218Same intake, but only spawn the `paid-research` agent. Render just the PAID block, with up to 5 channel rows and for each:
219
220- Expected CAC range (cite source or reasoning)
221- Creative angle suggestion
222- Starting budget
223- Attribution setup note (how `/marketing attribution` will measure it)
224- `Execute:` line pointing to the `/marketing` sub-command or `manual`
225
226End with the same handoff prompt as `plan`, scoped to paid channels.
227
228---
229
230## unpaid — organic deep-dive
231
232Spawn `unpaid-research` only. For each recommended channel output:
233
234- Why it fits (fit signals from intake)
235- First-30-days concrete actions (3 bullets)
236- Time-to-signal
237- Measurement: which `/marketing` sub-command tracks it (`/marketing seo`, `/marketing email`, `/marketing instagram`) or `manual + tool`
238- Lifecycle email is first-class here — recommend specific Klaviyo flows and note that `/marketing email` can scaffold them
239
240---
241
242## sales — sales motion
243
244Spawn `sales-research` only. Produce:
245
2461. **Motion pick** with one-paragraph rationale (Outbound / Inbound / PLG / Channel — Rule 1: these are the exact 4 options if you need the user to choose).
2472. **ICP slice** — which segment to hit first, sized from intake.
2483. **30/60/90 plan** — week-by-week activities (e.g. week 1: build list of 500 accounts; week 2: 200 outbound opens; …).
2494. **Tooling** — CRM, enrichment, sequencer; note when AI automation from the automation section fits.
2505. **Handoff** — offer `[Automate outreach via /gtm automation, Skip, Edit motion]`.
251
252---
253
254## automation — AI automation playbook
255
256Spawn `automation-research` only. Render each recipe with:
257
258- Trigger condition (what event fires it)
259- Model / tool stack (default to Claude + the ops tool listed in the catalog)
260- Integration point — specifically, which `/marketing` sub-command or external system it reads from and writes to
261- Risk flags (PII, cost, brand-voice drift) and the guardrails that mitigate them
262- Starter prompt / pseudo-code snippet so the user can copy-paste
263
264End with `AskUserQuestion` offering `[Scaffold recipe now, Save only, Pick different recipe]`.
265
266---
267
268## launch — 30/60/90 launch calendar
269
270Used at stage = pre-launch or beta. Produces a week-by-week calendar of launch activities across all four avenues.
271
272Required pre-flight checklist (render and check what's ready vs open):
273
274```
275☐ Positioning brief → /gtm brief
276☐ Landing page live → manual
277☐ Analytics wired → /marketing setup (GA4 + GSC)
278☐ Email capture live → /marketing email (Klaviyo list)
279☐ Ad accounts ready → /marketing setup (Meta, Google)
280☐ Social handles claimed → manual
281☐ Product Hunt / HN plan → this skill, below
282☐ Press / creator list → manual
283```
284
285Launch-day playbook: render hourly timeline for T-7d through T+14d, with concrete actions and the `/marketing` command (or manual step) for each.
286
287---
288
289## brief — one-page positioning brief
290
291Fast path — does NOT spawn the four research agents. Just intake + a single call to write the brief. Fields: **ICP**, **Pain**, **Value prop**, **3 messaging pillars**, **Proof points**, **Anti-positioning (who it's NOT for)**. Save to `${CLAUDE_PLUGIN_DATA_DIR}/gtm/<project-slug>-brief-$(date +%Y-%m-%d).md`.
292
293This is the cheapest entry point — recommend running `/gtm brief` before `/gtm plan` when the project's positioning isn't already written down.
294
295---
296
297## setup
298
299Configure GTM defaults so subsequent runs skip the intake questions. Per Rule 4, run every Bash call with `run_in_background: true` unless the result is needed for the very next decision.
300
301**Auto-scan (background) first:**
302
303```bash
304# Existing prefs
305jq -r '{project: .gtm_default_project, audience: .gtm_default_audience, voice: .gtm_brand_voice, budget: .gtm_monthly_budget, stage: .gtm_stage}' "$PREFS_PATH" 2>/dev/null
306
307# Repo signals
308git -C "$PWD" remote get-url origin 2>/dev/null
309head -50 README.md 2>/dev/null
310ls .planning/ 2>/dev/null
311```
312
313Then prompt for what's missing (≤4 options per Rule 1), in this order:
314
3151. **Default project name** — free-text, pre-filled from git remote slug
3162. **Project type** — `[B2B SaaS, B2C product, Marketplace, Dev tool / API]`
3173. **Stage** — `[Pre-launch, Beta, GA, Scale]`
3184. **Monthly budget tier** — `[<$1k, $1k–5k, $5k–25k, $25k+]`
3195. **Brand voice** — `[Playful, Professional, Technical, Bold]`
320
321Save to `$PREFS_PATH` as `gtm_default_project`, `gtm_project_type`, `gtm_stage`, `gtm_monthly_budget`, `gtm_brand_voice`. Never write API keys here — GTM does not own any credentials (`/marketing` does).
322
323Finish with a smoke test: run `/gtm brief` in background and report `✓ setup complete — try /gtm plan` or `✗ [error]`.
324
325---
326
327## Plugin Rules compliance (required reading)
328
329All behavior above respects `claude-ops/CLAUDE.md`:
330
331- **Rule 0 — public repo**: every example above uses `your-project`, `you@example.com`, `<YOUR_TOKEN>`. Never save user-specific data outside `$PREFS_PATH` or `${CLAUDE_PLUGIN_DATA_DIR}/gtm/`.
332- **Rule 1 — ≤4 options per AskUserQuestion**: every prompt in this file lists exactly ≤4. Paginate with `[More options...]` if a dynamic list grows past 4.
333- **Rule 3 — never auto-skip**: on launch handoff, every plan item gets an explicit `[Launch, Skip, Edit first]` prompt. No silent skipping.
334- **Rule 4 — background by default during setup**: all Bash calls in the `setup` flow use `run_in_background: true`.
335- **Rule 5 — destructive actions need explicit confirmation**: `/gtm` never spends money or sends messages directly — it delegates to `/marketing`, which owns per-action confirmation. Recommendations are just that.
336
337---
338
339## Why this skill is thin
340
341`/gtm` deliberately does NOT re-implement channel APIs. Credential resolution, curl calls, daemon data, and dashboards all live in `/marketing`. This skill is a strategy-and-handoff layer. If a capability belongs to a channel API, add it to `/marketing`; if it belongs to planning, it goes here.
342
343---
344
345**Source:** [`davepoon/buildwithclaude`](https://github.com/davepoon/buildwithclaude) → `plugins/claude-ops/skills/ops-gtm/SKILL.md`