define-brand-platform — Claude Code command: what it does
define-brand-platform turns positioning, messaging pillars, tone and a rollout plan into a deck, a narrative or a workspace document.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/define-brand-platform.mdWhat define-brand-platform does
Five steps. It pulls research and go-to-market goals together, drafts purpose, promise, pillars, proof points and tone guidance, then maps customer stories and metrics onto each pillar. Feedback from executives, product and sales comes next, and the run closes with a rollout plan.
Arguments cover audience (enterprise, smb, developer, partner), a comma-separated proof list (kpi, customer, analyst, product, roadmap), format as deck, narrative or workspace, plus optional constraints for legal and naming guardrails and references to existing research. You get a deck or narrative with positioning statements, pillars and a messaging matrix, a proof asset map, and a rollout plan with milestones, owners and success metrics. Two subagents, brand-foundation-architect and brand-governance-lead, carry the narrative and governance work; the brand-narrative-playbook and brand-voice-glossary skills keep the template and vocabulary in line.
--format takes three values only, so --format pdf gets you nothing. The command file sits at .claude/commands/define-brand-platform.md and is called through the plugin namespace: /brand-strategy:define-brand-platform. Validation depends on feedback from executives, product and sales; skip that and the platform stays one person's draft.
What it helps with
- write positioning and messaging pillars for a new segment
- tie customer stories and metrics to each pillar
- codify tone of voice and vocabulary in one place
- build a rollout plan with owners and success metrics
- turn scattered research into an executive deck
Example prompts for the agent
- /brand-strategy:define-brand-platform --audience enterprise --proof kpi,customer --format deck
- Draft the brand narrative for developers:
/brand-strategy:define-brand-platform --audience developer --proof product,kpi --format narrative - Rework the platform for localization:
/brand-strategy:define-brand-platform --format workspace --constraints localization
How to install define-brand-platform
Manually: put the files in place
.claude/commands/define-brand-platform.mdCall it with /define-brand-platform. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/define-brand-platform.mdCall it with /prompts:define-brand-platform. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/define-brand-platform.prompt.mdManually: put the files in place
.gemini/commands/define-brand-platform.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about define-brand-platform
How do I install define-brand-platform in Claude Code?
Copy the command file to .claude/commands/define-brand-platform.md in your project. From there it is called as /brand-strategy:define-brand-platform.
What does define-brand-platform do?
It builds a brand platform: positioning, messaging pillars, proof mapped to each pillar, tone guidance and a rollout plan. Output arrives as a deck, a narrative or a workspace document.
Which arguments does the command take?
--audience for the segment, --proof as a comma-separated list of proof types, --format (deck, narrative or workspace), and optionally --constraints and --references.
Source text
define-brand-platform.md · Apache-2.0
--- name: define-brand-platform description: Builds brand platform with positioning, pillars, tone, and rollout plan. usage: /brand-strategy:define-brand-platform --audience enterprise --proof kpi,customer --format deck --- # Command: define-brand-platform ## Inputs - **audience** – primary audience or segment focus (enterprise, smb, developer, partner). - **proof** – comma list of proof asset types to highlight (kpi, customer, analyst, product, roadmap). - **format** – deck | narrative | workspace. - **constraints** – optional guardrails (legal, regulatory, naming, localization). - **references** – URLs/docs of existing research, messaging, or campaigns. ## Workflow 1. **Discovery Alignment** – absorb research, GTM goals, competitive narratives. 2. **Narrative Drafting** – craft purpose, promise, pillars, RTBs, and tone guidance. 3. **Proof Mapping** – align customer stories, metrics, product proof to each pillar. 4. **Validation & Iteration** – gather feedback from execs, product, sales, customers. 5. **Rollout Plan** – define enablement, asset updates, KPIs, and governance owners. ## Outputs - Brand platform deck/narrative with positioning statements, pillars, and messaging matrix. - Proof asset map referencing customers, metrics, analysts, and demos. - Rollout & adoption plan with milestones, owners, and success metrics. ## Agent/Skill Invocations - `brand-foundation-architect` – leads narrative + stakeholder alignment. - `brand-governance-lead` – ensures compliance and rollout processes. - `brand-narrative-playbook` skill – enforces template + voice guardrails. - `brand-voice-glossary` skill – codifies tone, vocabulary, and localization notes. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents