Kai root note: knowledge/, harness/, and scripts/ paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a knowledge/ folder (the Kai plugin root, ~/.claude/kai, or the kai-cmo-harness repo). MARKETING.md, memory/, and any output files live in the current project. If a referenced scripts/ command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output.

Turn GTM work into something a client can actually act on: a set of linked web pages, not a folder of markdown. The hub is the deliverable; everything else hangs off it.

When to use

"GTM plan for [client]" / "go to market" / "put together a GTM" for a real client business
"Build the client hub" / "attach everything" / "package this for the client"
An engagement where the client must do things afterward (sign up for platforms, grant access, install tooling) and you want one link that walks them through it
Any deliverable that will be forwarded to a non-technical operator — pages, not files

When NOT to use

Planning itself — that's /kai-growth-plan (this skill packages the plan; it doesn't write it)
A single strategy page or customer-facing brochure with no hub and no follow-up actions — build just the page
Your own product's marketing — this is for client engagements with a handoff
Loose internal analysis nobody outside the team will read

kai-gtm-pack

When to use

When NOT to use

Workflow