home / skills / gtmagents / gtm-agents / brand-narrative-playbook

brand-narrative-playbook skill

/plugins/brand-strategy/skills/brand-narrative-playbook

This skill helps align messaging across audiences by organizing pillars, narrative arc, and proof into adaptable brand storytelling templates.

npx playbooks add skill gtmagents/gtm-agents --skill brand-narrative-playbook

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.3 KB

---
name: brand-narrative-playbook
description: Messaging and storytelling template that keeps positioning consistent
  across audiences.
---

# Brand Narrative Playbook Skill

## When to Use
- Defining or refreshing core messaging pillars.
- Translating positioning into talk tracks for different personas/channels.
- Auditing campaigns for narrative consistency.

## Framework
1. **Audience Grid** – ICP, persona, stage, key pain/aspiration.
2. **Narrative Arc** – context, tension, resolution, proof, call-to-action.
3. **Pillar Mapping** – tie each story beat to brand pillars and supporting evidence.
4. **Proof Library** – customers, metrics, analyst quotes, product demos.
5. **Adaptation Guide** – tone, length, channel tweaks, localization notes.

## Templates
- **Narrative Framework**: See `references/narrative_framework.md` for the arc and audience grid.
- **Messaging hierarchy doc** with prompts.
- **Storyboard slides** for exec, sales, product, and customer marketing audiences.
- **QA checklist** ensuring each asset hits pillar + proof requirements.

## Tips
- Keep a “retire/refresh” log for outdated proof.
- Include “watch-outs” for overused phrases or compliance issues.
- Pair with `define-brand-platform` to auto-populate pillar content.

---

Overview

This skill provides a production-ready Brand Narrative Playbook for keeping positioning and messaging consistent across audiences and channels. It packages a repeatable framework, templates, and checklists to turn brand pillars into persona-focused talk tracks and campaign assets. Use it to align GTM teams on story, proof, and adaptation rules.

How this skill works

The playbook inspects audience segments and maps each to a Narrative Arc (context, tension, resolution, proof, CTA). It ties story beats to core brand pillars and pulls supporting proof from a configurable library of customers, metrics, and demos. Templates and a QA checklist help generate and audit assets for tone, length, and channel-specific adaptations.

When to use it

Defining or refreshing core messaging pillars and positioning
Translating positioning into talk tracks for specific personas or stages
Auditing campaigns and content for narrative and proof consistency
Preparing executive, sales, product, or customer marketing storyboards
Localizing messages while preserving pillar alignment

Best practices

Start with an Audience Grid: ICP, persona, stage, and primary pain or aspiration
Map each narrative beat to at least one brand pillar and one piece of proof
Keep a retire/refresh log to avoid using stale customer proof or metrics
Use the Adaptation Guide to set tone, length, and channel-specific constraints
Run the QA checklist on every asset to ensure pillar + proof coverage

Example use cases

Create a sales talk track for a mid-market CTO addressing security and cost controls
Audit a multi-channel campaign to confirm consistent messaging and evidence
Build executive slides that follow the Narrative Arc and map to strategic pillars
Generate persona-specific email sequences that maintain the same positioning
Localize a product launch narrative while noting compliance watch-outs

FAQ

How does the playbook handle conflicting audience needs?

It uses the Audience Grid to prioritize pain points by persona and stage, then maps a single Narrative Arc that highlights the highest-priority tension and resolution while referencing secondary pillars as supporting evidence.

What counts as valid proof in the Proof Library?

Valid proof includes customer case studies, outcome metrics, analyst quotes, product demo results, and verified third-party endorsements; keep a retire/refresh log to remove outdated items.