pm-gtm-v1

pm-gtm-v1, source of truth → fresh gate state → phase-gated plan → config-only rows

Input is a go-to-market goal: a launch, a period, a plan refresh. Output is a plan package: a fresh gate-state snapshot, a plan built phase by phase, a campaign-architecture narrative, channel and tracking planning rows, and a handoff record for the owner and whoever runs marketing operations.

This verb plans. It never spends, never posts, never configures a platform, and never touches a tag container. Execution stays human; implementation stays engineering's.

Seam discipline: this verb emits no engineering seam artifacts. When technical work emerges from planning, a pixel install, a container change, instrumentation, landing pages, it leaves as classified candidate rows routed to /pm-requirements-v1 (a single item) or /pm-portfolio-v1 (a batch). One seam, one owner.

Preflight (run first)

PKG_ROOT="${CLAUDE_PLUGIN_ROOT:-${PKG_ROOT:-}}"
[ -n "$PKG_ROOT" ] && [ -r "$PKG_ROOT/.claude-plugin/plugin.json" ] || { echo "STOP: set PKG_ROOT to this package's root directory, the one holding .claude-plugin/plugin.json, then re-run."; exit 2; }
bash "$PKG_ROOT/scripts/preflight.sh" pm-gtm-v1 [--stack <keys>]

Conditional keys: gate-state-snapshot (the read-only analytics reads that let a gate state be measured rather than asserted) · workspace-docs · backlog-sync. A selected-conditional miss blocks like a required one.

Standalone vs supercharged. Standalone (python3): the full chain resolve, the phase-gated plan, the campaign narrative and the config-only rows, with every unprobeable gate state written NEEDS-CONFIRMATION with a named confirmer, never guessed. Supercharged: gate-state-snapshot turns those rows into measured states.

There is deliberately no advertising-platform capability. Nothing here holds or requests ad-account credentials, which is precisely why the rows in step 4 are configuration proposals rather than changes.