pm-gtm-v1

Solid

Go-to-market and growth planning, GTM here means go-to-market, never a tag-manager container. Use when a growth plan needs building or refreshing: "build the go-to-market plan", "growth plan for <period or launch>", "campaign architecture", "channel plan", "media plan", "tracking planning rows", "update the growth plan after <release>". It resolves which plan document is actually current, takes a FRESH gate-state snapshot before planning a single sentence, builds the plan phase by phase, narrates the campaign architecture per channel and per persona, and emits channel and tracking rows CONFIG-ONLY, no credentials, no platform writes, no spend. NOT for executing campaigns or buying media; NOT for implementing tracking (that is engineering work, routed through pm-requirements-v1); NOT for writing a handoff package or scoring a backlog.

AI & Automation 70 stars 3 forks Updated 1 weeks ago MIT

Install

Quality Score: 85/100

Stars 20%

62

Recency 20%

90

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

80

License 10%

100

Description 5%

100

Skill Content

# 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) ```bash 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.** ...

Details

Author: naderelewa
Repository: naderelewa/Product-to-Prod
Created: 4 weeks ago
Last Updated: 1 weeks ago
Language: Shell
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

gtm

Phased go-to-market for startup products. Builds a GTM playbook from upstream artifacts (validation-canvas, pitch-deck, brand-workshop), produces multi-channel content, schedules cadenced tasks, enforces compliance (CAN-SPAM/GDPR/FTC), emits handoff events. Trust ramp P1→P2→P3 (read-only → scheduled → autonomous). Project-local `.gtm/`. Kill switch via HALT file. Triggers on "set up GTM", "create a launch plan", "build a marketing playbook", "kick off go-to-market", "schedule social posts", "post-launch marketing", "growth ops", "draft launch content", or having pipeline output and asking "what's next for getting users". Single-channel asks for a startup product also trigger. NOT for brand identity (`brand-workshop`), pitch decks (`pitch-deck`), lean canvas (`validation-canvas`), adversarial review (`startup-grill`), one-shot non-startup content (`marketing:content-creation`), CRM/sales. NOT Google Tag Manager (different "GTM"). NOT the idiom "going to market with findings".

1 Updated 1 months ago

AI & Automation Listed

pm-gtm

产品上市（Go-to-Market）技能。覆盖 6 个模块：滩头市场选择、理想客户画像（ICP）、GTM 策略、 7 种 GTM 打法（Inbound / Outbound / 付费投放 / 社区 / 伙伴 / ABM / PLG）、5 类增长循环（病毒 / 使用 / 协作 / UGC / 推荐）、竞品销售战报卡。能力：(1) 定「第一个市场打谁」和「理想客户长什么样」(2) 选打法组合并算增长循环系数 (3) 出完整上市计划与销售对抗物料。触发词：「上市计划」「GTM」「怎么打开市场」「第一批客户找谁」「滩头市场」「ICP」「理想客户画像」「增长循环」「病毒增长」「飞轮」「获客渠道怎么选」「PLG」「ABM」「发布计划」「战报卡」「销售话术」「客户问为什么不选竞品」，或者用户在问「产品做好了但卖不动」「该投哪个渠道」时。不适用：战略方向与定价 → pm-strategy-frameworks；定位语/命名/北极星指标 → pm-growth-marketing；竞品四维深度拆解 → pm-competitor-deconstructor（战报卡是销售用的对抗物料，不是分析报告）；发版说明 → pm-release-notes。参考文档为英文原文，产出语言跟随用户提问语言。

2 Updated 4 days ago

Web & Frontend Solid

pm-requirements-v1

The requirements cycle, turn a strategy statement, a release target and a set of affected surfaces into an evidence-tagged, gated HANDOFF PACKAGE: spec.md, plan.md, data-model.md, contracts/, slices.json, a design gate and a case contract, plus the record that makes all of it auditable. Five phases: P0 context lock (the north-star metric elicited fresh every cycle) → P1 research → P2 strategy → P3 product spec → P4 handoff. Use when someone says "run the requirements cycle", "write the PRD / handoff package for <feature>", "prep the design gate", "requirements for the next release", or hands a strategy statement that needs to become buildable work. NOT for writing code, running CI, deploying or merging, an engineering toolchain owns those; NOT for release verification (pm-verify-release-v1); NOT for scoring a backlog batch (pm-portfolio-v1).

70 Updated 1 weeks ago