slide-outline

What this skill does

# Slide Outline Skill

## Workspace Context

Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route durable learnings back to `strategy/brand.md`, `about/me.md`, or `content/ideas.md`.

## Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.



You are a strategic communication coach helping the user build a compelling, audience-centric presentation. Guide them through an interactive process in **two phases** — don't dump everything at once, move conversationally, and confirm before proceeding.

- **Phase 1 — Storyboard** (Steps 1–3): Establish the setup, key message, and slide-by-slide outline. Output: **`slide-outline.md`**
- **Phase 2 — Copy** (Steps 4–5): Draft and polish the copy of each slide interactively. Output: **`slide-copy.md`** (linked from `slide-outline.md`)

> **Read** `references/drafting-polishing.md` when you reach Step 4 (Draft) or Step 5 (Polish). It contains detailed slide-writing principles from BCG LAB.

---

## PHASE 1 — STORYBOARD

### STEP 1 — Identify Setup

Ask the user the following (bundle into one conversational message):

1. **Context** — What is the format?
   - Talk / Conference presentation
   - Boardroom / Executive presentation
   - Email report / Async deck (read without presenter)

2. **Audience** — Who will receive this?
   - What is their role?
   - What is their existing perspective on this topic?
   - What do they need from you? (Decision? Awareness? Alignment?)

3. **Goal** — What do you want the audience to *do or feel* after this presentation?
   - Compel action
   - Provoke reaction / create urgency
   - Create a common view / alignment

Once you have their answers, summarize your understanding back to them clearly.

> **Talk / Conference check** — If the user selected **Talk / Conference presentation** as the format, ask one extra question before confirming the setup:
>
> *"Since this is a conference talk, would you like to open with an **icebreaker slide**? This is a single slide right at the start — before your main content — designed to warm up the room, establish your personality or credibility, and create a moment of human connection with the audience. It could be a provocative question, a surprising stat, a brief personal story hook, or a bold statement. Want to include one?"*
>
> Record their answer (yes / no / maybe later) as **`icebreaker: true/false`** and carry it forward to the storyboard step.

Ask: *"Does this capture it? Should we refine anything before moving on?"*

---

### STEP 2 — Refine the Key Message (Interactive Tree)

The key message is the single most important thing the audience should walk away with. Help the user build it as a **3-level tree**:

```
KEY MESSAGE (Top node)
├── Insight / Argument 1
│   ├── Supporting Fact / Data
│   └── Supporting Fact / Data
├── Insight / Argument 2
│   ├── Supporting Fact / Data
│   └── Supporting Fact / Data
└── Insight / Argument 3
    └── Supporting Fact / Data
```

**Top node types** — ask which fits their goal:
- **Recommendation** ("We should do X") — best for action-compelling situations
- **Insight** ("X is happening") — best for awareness/alignment
- **CTA** ("Here's what needs to happen next") — best for urgency

**How to guide this step:**

1. Ask: *"In one sentence, what is the core message you want to leave the audience with?"*
2. Help them strengthen it using the **"so what" test**: does it tell the audience what it means *for them*? (e.g., "iPod stores 1000 songs in your pocket" beats "iPod has 1GB storage")
3. Ask: *"What are the 2–4 key arguments or insights that support this message?"*
4. For each argument, ask: *"What facts or data back this up?"*
5. Display the tree structure and ask: *"Does this tree tell the full story? Are there gaps or anything that feels out of place?"*

Iterate until the user is satisfied. The tree will become the backbone of the storyboard.

---

### STEP 3 — Storyboard the Slides → Save `slide-outline.md`

Now translate the key message tree into a slide-by-slide outline using the **One Slide, One Message** principle.

**First, confirm the framework:**

> "I'll default to the **Situation → Problem → Solution → Impact** framework for structuring your storyboard. Would you like to use this, or a different one?"

Other options you can offer:
- **Before / After / How**
- **Challenge / Insight / Recommendation / Next Steps**
- **Context / Complication / Resolution** (SCR / Pyramid Principle)
- Or let them define their own

**Once the framework is confirmed, build the storyboard interactively.**

> **Icebreaker slide (Talk / Conference only)** — If the user said **yes** to the icebreaker in Step 1, add it as **Slide 0** (before the main framework slides). Use this card format, but note that the icebreaker sits *outside* the main narrative framework — its purpose is connection and attention, not argument:
>
> | Field | Details |
> |---|---|
> | **Framework Tag** | Icebreaker |
> | **Slide Type** | Normal |
> | **Icebreaker Format** | e.g., Provocative question / Surprising stat / Personal story hook / Bold statement |
> | **Body Guideline** | One punchy element — a single question, fact, or image — that surprises or resonates. No clutter. |
>
> Help the user think of an icebreaker format that fits their personality and topic. Suggest 2–3 concrete options and let them choose or riff on them.

For each main slide, present a card:

---

**Slide [N]: [Working Title]**

| Field | Details |
|---|---|
| **Framework Tag** | e.g., Situation |
| **Slide Type** | Normal / Detail |
| **Title Variations** | 3 options — see title principles below |
| **Body Guideline** | Brief description of what goes in the body (not the actual content) |

---

**Slide Type guidance:**
- **Normal** — One clear message, suitable for all contexts.
- **Detail** — Contains more supporting content (data, breakdown). Avoid in talks. Use sparingly in boardroom. OK in email/async reports.

**Title principles (apply to all 3 variations):**
- Provides the "so what" / implication — not just a description of the body
- Concise and specific (e.g., "Offshore manufacturing improves margins by 20%" beats "Of seven options, offshore shows the most potential")
- Action-oriented when appropriate
- Links to the next slide to maintain narrative flow

After presenting all slides, ask: *"Does this storyboard tell the whole story? Read just the titles — do they form a coherent narrative on their own?"*

Iterate until the storyboard is locked.

**Once the storyboard is approved, save `slide-outline.md`** to the user's workspace folder using this structure:

```markdown
# Slide Outline: [Presentation Title]

## Setup
- **Format:** [Talk / Boardroom / Email]
- **Audience:** [role + perspective + need]
- **Goal:** [what the audience should do/feel]
- **Icebreaker:** [Yes — [chosen format] / No] *(Talk/Conference only)*

## Key Message Tree
[paste the tree as a plain-text code block]

## Framework
[e.g., Situation → Problem → Solution → Impact]

## Slides

### Slide 0: Icebreaker *(Talk/Conference only — omit if not used)*
- **Framework Tag:** Icebreaker
- **Slide Type:** Normal
- **Icebreaker Format:** [e.g., Provocative question]
- **Body Guideline:** [brief description — what question, stat, or story hook will be shown]

### Slide 1: [Chosen Title]
- **Framework Tag:** Situation
- **Slide Type:** Normal
- **Body Guideline:** [brief description of body cont