Ops Gtm

OPS ► GTM COMMAND CENTER

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

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

   • 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

2. 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.

3. Daemon health: Read ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json. If action_needed is not null, surface it before running any long planning flow.

4. 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

5. /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:

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

See references/catalog.md.

plan — full GTM plan (default)

1. Intake per Project Intake section.

2. Spawn the four research agents (Agent Teams if flag set, else fire-and-forget).

3. 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
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

4. 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.

5. 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