GTM Positioning

Go-to-market ContentPack: offers, positioning, messaging pillars, ICPs, campaigns, battle cards, and proof points.

MIT. Dual-host: Claude Code, Grok Build, and Codex (Agent Skill Standard). Writes OKF Markdown + YAML into a shared second-brain bundle so other agents and local jobs can read the same graph.

Install

# Claude Code
/plugin marketplace add SpillwaveSolutions/gtm-positioning
/plugin install gtm-positioning@SpillwaveSolutions

# Skilz CLI
skilz install SpillwaveSolutions/gtm-positioning

Point the plugin at a shared knowledge root (default knowledge/). All sibling ContentPack plugins write into the same tree.

Skills

Skill	What it does
`/gtm-init`	Scaffold the catalogs this plugin owns
`/gtm-capture`	Capture a noun into the shared second brain (deterministic write)
`/gtm-pack`	Build a bounded ContextPack from a root concept
`/gtm-validate`	Validate frontmatter, types, and links
`/gtm-session`	Open or close an isolated write session (worktree + PR)
`/gtm-doctor`	Health check of the bundle this plugin owns

Nouns this plugin may write

Type	Meaning
`Offer`	Sellable engagement or product
`PositioningStatement`	How we win the category
`MessagingPillar`	Repeatable message
`ValueProposition`	Why it matters to a buyer
`IdealCustomerProfile`	Who we sell to
`CompetitiveAlternative`	What they would do instead
`Objection`	GTM-level buyer concern
`CaseStudy`	Proof story
`ProofPoint`	Quantified or qualitative proof
`LandingPage`	Page that carries an offer
`SiteStatus`	Current site / offer page state
`TrafficSource`	How people arrive
`ConversionEvent`	Desired action
`Campaign`	GTM motion
`Experiment`	Message or page test
`PricingNote`	Packaging or price signal
`Packaging`	How the offer is bundled
`Testimonial`	Customer quote
`BattleCard`	How to talk vs an alternative

Relationships

`rel`	Meaning
`owned_by`	GTM owner identity
`promoted_by`	Campaign or article promotes offer
`aimed_at`	Offer aimed at an ICP
`supported_by`	Proof point or case study
`competes_with`	Alternative
`tested_by`	Experiment
`related_to`	Soft association
`originates_from`	Provenance

Catalogs

offers/
positioning/
campaigns/
icps/
proof-points/
battle-cards/
experiments/

Deterministic write boundary

The model proposes. Schema-enforced scripts commit:

python3 scripts/gtm_common.py write \
  --bundle knowledge \
  --type Offer \
  --folder offers \
  --title "Example" \
  --author "Grok Bot: GTM Positioning"

Never invent rel values. Never write types owned by another plugin.

Related plugins

ContentPack suite

Foundation

okf-plugin — Open Knowledge Format graph engine
project-knowledge-capture — Project Knowledge Capture. The why second brain.
system-architecture-capture — System Architecture Capture. The what-is-running second brain.
data-engineering-knowledge-capture — Data Engineering Knowledge Capture. The data-plane second brain.
wiki_ticket_sdd — WikiTicket SDD. Visible work log. Append-only ULID JSONL plus fold.
okf-agent-graph — AGER. Orchestrator / Doer / Judge / Synthesizer.

Onboarding

Grok Bot and other host agents should start at docs/ONBOARDING.md. That file is the history of the LLM-wiki effort, the destination state (Grok Bots and local agents sharing one git-native second brain), and the canonical public repo list.

Multi-host

Works with Claude Code, Grok Build, Codex, Cursor, Agent Plugins 1.0 clients, Grok Bot, and LangChain Deep Agents.

Host	How to load
Claude Code	marketplace + plugin install
Grok Build	zero-config Claude plugin
Codex	Agent Skills / `hooks/hooks.json`
Agent Plugins clients	root `plugin.json` + `skills/`
Grok Bot	docs/GROK_BOT.md
Cursor	docs/CURSOR.md — `.cursor-plugin` + Agent Plugins 1.0
LangChain Deep Agents	docs/LANG_CHAIN_DEEP_AGENTS.md

Write isolation (worktree + PR) lives in second-brain-core: docs/ISOLATION.md. Point SECOND_BRAIN_ROOT at the session bundle. Never hard-code a private remote.

Eight job-function plugins plus core. Knowledge root is always a local path or env the human already owns.

spillwavesolutions/gtm-positioning