If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
Sales Playbook
Get or structure a sales playbook with repeatable motions (who, when, how, assets) for discovery, demo, negotiation, and closing. This skill works with knowledge base when connected; otherwise structures a standard playbook from context and notes "Customize with your playbook from knowledge base."
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ SALES PLAYBOOK │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ Structure motions: discovery, demo, negotiation, closing │
│ ✓ Per motion: who (owner), when (trigger), how (steps), assets │
│ ✓ Output: playbook doc with motions list + per-motion detail │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~knowledge base~~: Pull existing playbook doc, scripts, battlecards │
│ + ~~CRM~~: Stage-specific playbook steps, win/loss patterns │
└─────────────────────────────────────────────────────────────────┘
Output Structure
- Motions list: Discovery, Demo, Negotiation, Closing (or user-specified motions).
- Per-motion detail: Who (owner), When (trigger), How (steps), Assets (links or docs).
- Source:
knowledge base or user-provided. If knowledge base not connected, note "Customize with your playbook from knowledge base."
Data Sources (per REFERENCE.md)
knowledge base (if connected): Sales playbook doc, demo script, battlecards, case studies.CRM (if connected): Stage definitions, win/loss patterns (optional).- User input: Motion type focus, custom motions.
1---2name: sales-playbook3description: Get or structure a sales playbook from ~~knowledge base~~ or context. Repeatable motions (who, when, how, assets) for discovery, demo, negotiation, and closing. Trigger with "get sales playbook", "what's our playbook for [motion]", or use the /get-sales-playbook command.4---56> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).78# Sales Playbook910Get or structure a sales playbook with repeatable motions (who, when, how, assets) for discovery, demo, negotiation, and closing. This skill works with ~~knowledge base~~ when connected; otherwise structures a standard playbook from context and notes "Customize with your playbook from ~~knowledge base~~."1112## How It Works1314```15┌─────────────────────────────────────────────────────────────────┐16│ SALES PLAYBOOK │17├─────────────────────────────────────────────────────────────────┤18│ ALWAYS (works standalone) │19│ ✓ Structure motions: discovery, demo, negotiation, closing │20│ ✓ Per motion: who (owner), when (trigger), how (steps), assets │21│ ✓ Output: playbook doc with motions list + per-motion detail │22├─────────────────────────────────────────────────────────────────┤23│ SUPERCHARGED (when you connect your tools) │24│ + ~~knowledge base~~: Pull existing playbook doc, scripts, battlecards │25│ + ~~CRM~~: Stage-specific playbook steps, win/loss patterns │26└─────────────────────────────────────────────────────────────────┘27```2829---3031## Output Structure3233- **Motions list:** Discovery, Demo, Negotiation, Closing (or user-specified motions).34- **Per-motion detail:** Who (owner), When (trigger), How (steps), Assets (links or docs).35- **Source:** ~~knowledge base~~ or user-provided. If ~~knowledge base~~ not connected, note "Customize with your playbook from ~~knowledge base~~."3637---3839## Data Sources (per REFERENCE.md)4041- **~~knowledge base~~** (if connected): Sales playbook doc, demo script, battlecards, case studies.42- **~~CRM~~** (if connected): Stage definitions, win/loss patterns (optional).43- User input: Motion type focus, custom motions.
propane-ai