@ztffn/presentation-generator-plugin 1.0.0

package/skills/presentation-generator/SKILL.md

@@ -0,0 +1,190 @@
+---
+name: presentation-generator
+description: >
+  Generate complete graph-based presentations from natural language briefs and/or project documents.
+  Use when asked to create, generate, build, or design a presentation, pitch deck, or slide deck.
+  Triggers on: "create a presentation", "build a deck", "generate slides", "make a pitch",
+  "presentation for", "slide deck about".
+---
+
+# Presentation Generator
+
+Orchestrates a three-agent pipeline to produce a complete, navigable presentation graph JSON from a user brief and optional source documents.
+
+## Pipeline Overview
+
+```
+User Brief + Documents
+        ↓
+  [1] Content Extraction  →  _temp/presentation-content-brief.json
+        ↓
+  [2] Narrative Design     →  _temp/presentation-outline.md
+        ↓
+  [3] User Approval        →  confirm or revise structure
+        ↓
+  [4] Design & JSON        →  _temp/presentation-draft.json
+        ↓
+  [5] Delivery             →  import instructions + media checklist
+```
+
+## Phase 1 — Context Gathering
+
+Parse the user's request to identify:
+
+1. **What** is being presented (product, project, topic)
+2. **To whom** (audience type, their background, what they care about)
+3. **For what goal** (`pitch`, `demo`, `update`, `internal`, `exploratory`)
+4. **Source documents** — paths to files the user wants to draw from
+
+If no documents are provided, skip Phase 2 and construct a minimal content brief directly from the prompt. Ask the user for any missing critical information:
+- If audience is unclear, ask who the presentation is for
+- If goal is unclear, ask what outcome they want
+
+## Phase 2 — Content Extraction
+
+Invoke the `presentation-content` sub-agent:
+
+```
+Agent: presentation-content
+Input: List of document paths from the user
+Output: _temp/presentation-content-brief.json
+```
+
+The content agent reads all source documents and writes a structured content brief.
+
+### Brief Quality Gate
+
+After the content brief is written, read `_temp/presentation-content-brief.json` and verify:
+
+1. **`keyMessages`** contains 3-5 declarative claims (subject + verb + specific claim), not topic labels
+   - BAD: "Our technology"
+   - GOOD: "Calora reduces industrial heat costs by 40% with no infrastructure replacement"
+
+2. **`dataPoints`** contains at least one entry with a specific number in `value`
+   - BAD: `{ "value": "significant" }`
+   - GOOD: `{ "value": "40%", "source": "Field trial, Oslo 2024" }`
+
+3. **`callToAction`** is a single actionable sentence with an action verb
+   - BAD: "Let's continue the conversation"
+   - GOOD: "Agree to a structured 3-month pilot at the Stavanger facility starting Q2"
+
+If any check fails, ask the user ONE targeted question to fill the gap. Do not pass a weak brief to the narrative agent.
+
+## Phase 3 — Narrative Design
+
+Invoke the `presentation-narrative` sub-agent:
+
+```
+Agent: presentation-narrative
+Input: Reads _temp/presentation-content-brief.json
+Output: _temp/presentation-outline.md
+```
+
+The narrative agent selects a story framework, designs the spine and drill-down structure, and writes a detailed slide outline.
+
+## Phase 4 — User Approval
+
+Read `_temp/presentation-outline.md` and render it as a folder tree for the user:
+
+```
+Cover: [headline]
+Problem: [headline]
+  └─ Detail: [headline]
+  └─ Root Cause: [headline]
+Solution: [headline]
+  └─ How It Works: [headline]
+Value: [headline]
+  └─ Case Study: [headline]
+Call to Action: [headline]
+```
+
+**Rules:**
+- Top-level items are spine nodes (horizontal navigation)
+- Indented items with `└─` are drill-down children (vertical navigation)
+- Siblings at the same indent level are horizontal peers within their branch
+
+Write the tree to `_temp/presentation-plan.md` and present it in the chat.
+
+Wait for the user to respond:
+- **"approved"** or similar → proceed to Phase 5
+- **change requests** → update the outline, re-render the tree, wait again
+- **"start over"** → return to Phase 1
+
+This loop continues until the user explicitly approves.
+
+## Phase 5 — Design and JSON Generation
+
+Invoke the `presentation-design` sub-agent:
+
+```
+Agent: presentation-design
+Input: Reads _temp/presentation-outline.md
+Output: _temp/presentation-draft.json
+```
+
+The design agent translates each slide into a fully specified graph node, wires all edges with bidirectional pairs, and validates the result.
+
+## Phase 6 — Delivery
+
+After `_temp/presentation-draft.json` is written:
+
+1. Confirm the JSON was written successfully
+2. Provide import instructions:
+
+```
+Import your presentation:
+1. Open the graph editor at /present/plan
+2. Click "New presentation"
+3. Choose "Import JSON"
+4. Select _temp/presentation-draft.json
+```
+
+3. If any slides have video placeholders, list them:
+
+```
+Slides requiring manual video upload:
+- "[Slide Title]" — [description of needed video]
+
+Upload path: POST /api/slide-images/upload
+Accepted: image/*, video/mp4, video/webm, video/quicktime (max 50MB)
+Replace the PLACEHOLDER string with the returned URL after upload.
+```
+
+## Sub-Agent Reference
+
+| Agent | Skills Loaded | Purpose |
+|---|---|---|
+| `presentation-content` | `narrative/content-signals` | Extract structured brief from documents |
+| `presentation-narrative` | `narrative/frameworks`, `narrative/slide-content`, `narrative/graph-topology` | Design story structure and slide content |
+| `presentation-design` | `system/node-schema`, `system/edge-conventions`, `system/layout-templates`, `system/positioning`, `examples/pitch-reference` | Translate outline to valid graph JSON |
+
+## Working Without Documents
+
+When the user provides only a verbal brief (no document paths):
+
+1. Skip Phase 2 entirely
+2. Construct the content brief yourself from the user's prompt:
+   - Ask clarifying questions for missing fields
+   - Populate what you can from the conversation
+   - Write the brief to `_temp/presentation-content-brief.json`
+3. Proceed to Phase 3 as normal
+
+## Large Document Sets
+
+If the user provides many documents that may exceed a single agent's context:
+
+1. Split the document list into groups of 3-5 files
+2. Invoke `presentation-content` multiple times, each with a subset
+3. Merge the partial briefs into a single content brief
+4. Run the quality gate on the merged brief
+
+## File Manifest
+
+All intermediate and output files:
+
+| File | Created By | Read By |
+|---|---|---|
+| `_temp/presentation-content-brief.json` | Content agent or orchestrator | Narrative agent |
+| `_temp/presentation-outline.md` | Narrative agent | Design agent, orchestrator |
+| `_temp/presentation-plan.md` | Orchestrator | User (approval) |
+| `_temp/presentation-draft.json` | Design agent | User (import) |

package/skills/presentation-generator/examples/pitch-reference.json

@@ -0,0 +1,155 @@
+{
+  "_comment": "Reference example: 7-node presentation demonstrating key slide types. Trimmed from _temp/presentation-demo-output.json. Each node shows a different design pattern the design agent should know how to produce.",
+
+  "_node_1_comment": "COVER NODE: centered, branded, brand font. Sets the context. No content-heavy text.",
+  "_node_2_comment": "CONTENT NODE: standard bullets, left-aligned (centered:false). Includes notes field for speaker context. The workhorse slide type.",
+  "_node_3_comment": "TWO-COLUMN NODE: layout:two-column splits on --- delimiter. Good for comparison or text+visual.",
+  "_node_4_comment": "INLINE CHART NODE: [chart:name] tag in content with charts record. Data supports the text argument.",
+  "_node_5_comment": "R3F SCENE NODE: type:r3f with scene config. lightText:true for dark background. Content overlays the 3D scene.",
+  "_node_6_comment": "BACKGROUND IMAGE NODE: Unsplash URL, overlay for readability, lightText. Mood-setting slide.",
+  "_node_7_comment": "CLOSING NODE: centered, branded, call to action. Mirrors cover structure.",
+
+  "nodes": [
+    {
+      "id": "cover",
+      "type": "huma",
+      "position": { "x": 0, "y": 0 },
+      "data": {
+        "label": "Graph-Based Presentations",
+        "topic": "Huma Showcase",
+        "content": "Non-linear storytelling for technical teams.\n\nNavigate with arrow keys. Press **down** to drill into any topic.",
+        "centered": true,
+        "brandFont": true,
+        "showBranding": true,
+        "brandingText": "huma.energy"
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    },
+    {
+      "id": "problem",
+      "type": "huma",
+      "position": { "x": 240, "y": 0 },
+      "data": {
+        "label": "The Problem",
+        "topic": "01 / Problem",
+        "content": "## Linear tools break complex stories\n\n- Cannot branch based on audience questions\n- Skipping sections breaks the flow\n- Presenters get lost navigating dense topics\n- No private view for speaker notes during screen share\n\nEvery meeting is different. The presentation should adapt.",
+        "notes": "Pause here and ask: 'Does this match what you experience with your current tooling?' — their answer shapes how much time to spend on this node. If they push back, the drill-down below has the data. Key talking point: the fourth bullet is the one that resonates most with technical presenters.",
+        "centered": false
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    },
+    {
+      "id": "value-detail",
+      "type": "huma",
+      "position": { "x": 240, "y": 150 },
+      "data": {
+        "label": "Value Breakdown",
+        "topic": "03 / Value",
+        "content": "## Flexible narratives\nAdapt flow to audience type and questions in real time\n\n---\n\n## Consistent style\nReuse front-end web styling and components directly\n\n## Professional delivery\nSpeaker notes and timing without the audience seeing them",
+        "layout": "two-column",
+        "centered": false
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    },
+    {
+      "id": "value",
+      "type": "huma",
+      "position": { "x": 480, "y": 0 },
+      "data": {
+        "label": "The Value",
+        "topic": "03 / Value",
+        "content": "## Why this approach wins\n\n[chart:value]\n\nAdapt to the audience. Reuse web components. Deliver with confidence.",
+        "charts": {
+          "value": {
+            "chartType": "radar",
+            "data": [
+              { "axis": "Flexibility", "graph": 95, "traditional": 30 },
+              { "axis": "Visual Quality", "graph": 90, "traditional": 50 },
+              { "axis": "Interactivity", "graph": 85, "traditional": 20 },
+              { "axis": "Ease of Use", "graph": 60, "traditional": 90 },
+              { "axis": "Consistency", "graph": 85, "traditional": 40 },
+              { "axis": "Tech Signal", "graph": 95, "traditional": 15 }
+            ],
+            "config": {
+              "xKey": "axis",
+              "yKeys": ["graph", "traditional"],
+              "showGrid": true,
+              "showLegend": true
+            }
+          }
+        },
+        "centered": false
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    },
+    {
+      "id": "feat-3d",
+      "type": "huma",
+      "position": { "x": 720, "y": 0 },
+      "data": {
+        "label": "3D Scenes",
+        "topic": "04 / Features",
+        "type": "r3f",
+        "scene": {
+          "component": "rotating-cube",
+          "controls": true,
+          "background": "#1a1a2e"
+        },
+        "content": "Interactive React Three Fiber scene.\n\nDrag to rotate. Scroll to zoom. Scenes load from a component registry.",
+        "lightText": true
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    },
+    {
+      "id": "feat-bgimage",
+      "type": "huma",
+      "position": { "x": 960, "y": 0 },
+      "data": {
+        "label": "Background Image",
+        "topic": "04 / Features",
+        "content": "## Full-bleed imagery\n\nUpload any image as a slide background. Toggle overlay for text readability.\n\n- Cover/contain fit modes\n- Dark overlay toggle\n- Light text auto-detection",
+        "backgroundImage": "https://images.unsplash.com/photo-1451187580459-43490279c0fa?w=1920&q=80",
+        "backgroundImageFit": "cover",
+        "backgroundImageOverlay": true,
+        "lightText": true,
+        "centered": false
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    },
+    {
+      "id": "end",
+      "type": "huma",
+      "position": { "x": 1200, "y": 0 },
+      "data": {
+        "label": "Get Started",
+        "content": "Fork this template to build your own.\n\nEvery slide, chart, and scene is editable in the graph editor.",
+        "centered": true,
+        "brandFont": true,
+        "showBranding": true,
+        "brandingText": "huma.energy"
+      },
+      "style": { "width": 180, "height": 70 },
+      "measured": { "width": 180, "height": 70 }
+    }
+  ],
+  "edges": [
+    { "id": "e-cover-problem", "source": "cover", "target": "problem", "sourceHandle": "s-right", "targetHandle": "t-left" },
+    { "id": "e-problem-cover", "source": "problem", "target": "cover", "sourceHandle": "s-left", "targetHandle": "t-right" },
+    { "id": "e-problem-value", "source": "problem", "target": "value", "sourceHandle": "s-right", "targetHandle": "t-left" },
+    { "id": "e-value-problem", "source": "value", "target": "problem", "sourceHandle": "s-left", "targetHandle": "t-right" },
+    { "id": "e-problem-detail", "source": "problem", "target": "value-detail", "sourceHandle": "s-bottom", "targetHandle": "t-top" },
+    { "id": "e-detail-problem", "source": "value-detail", "target": "problem", "sourceHandle": "s-top", "targetHandle": "t-bottom" },
+    { "id": "e-value-3d", "source": "value", "target": "feat-3d", "sourceHandle": "s-right", "targetHandle": "t-left" },
+    { "id": "e-3d-value", "source": "feat-3d", "target": "value", "sourceHandle": "s-left", "targetHandle": "t-right" },
+    { "id": "e-3d-bgimage", "source": "feat-3d", "target": "feat-bgimage", "sourceHandle": "s-right", "targetHandle": "t-left" },
+    { "id": "e-bgimage-3d", "source": "feat-bgimage", "target": "feat-3d", "sourceHandle": "s-left", "targetHandle": "t-right" },
+    { "id": "e-bgimage-end", "source": "feat-bgimage", "target": "end", "sourceHandle": "s-right", "targetHandle": "t-left" },
+    { "id": "e-end-bgimage", "source": "end", "target": "feat-bgimage", "sourceHandle": "s-left", "targetHandle": "t-right" }
+  ]
+}

package/skills/presentation-generator/examples/presentation-guide.md

@@ -0,0 +1,314 @@
+# The Presentation Playbook
+
+A practical guide for creating and delivering compelling presentations. Synthesizes frameworks from Nancy Duarte, Andy Raskin, Mike Maples Jr, Matthew Dicks, Tristan de Montebello, and others. References throughout for deep dives.
+
+---
+
+## Part 1 — Before You Open the Slide Software
+
+### Start With the Arrow
+
+Define the one thing you want the audience to remember before writing a single slide. Not a topic — a sentence. "Our customers waste 11 hours a week reconciling three systems that don't talk to each other." Everything else in the presentation is the bow: the anecdotes, data points, and comparisons that give that sentence weight and launch it into the room.
+
+If you cannot state your arrow in one sentence, you are not ready to build slides.
+
+→ Deep dive: *Bow and Arrow Technique* — Tristan de Montebello, Giving Presentations
+
+### Know Exactly Who Is in the Room
+
+Before writing a word, answer three questions:
+
+1. **Who specifically is in the room?** Their role, what they know, what they care about
+2. **What do they need to believe to take the action you want?** Not "understand" — *believe*
+3. **What objections will they raise, and do you have data ready for each one?**
+
+Casey Winters: "If you haven't thought through every question that might be asked, you're not prepared enough. You need to know the entire universe of how that meeting can go."
+
+For high-stakes presentations: run pre-meetings with key individuals before the formal review. Surface concerns early. No surprises in the room.
+
+→ Deep dive: *De-risking Presentations* — Casey Winters, Giving Presentations
+
+### Find the Earned Secret
+
+Identify the non-obvious insight that makes your argument urgent *right now*, not three years ago or three years from now. This is not a product feature — it is a shift in the world:
+
+- A regulatory change that makes the old approach non-compliant
+- A cost inflection that makes the status quo unaffordable
+- A technology shift that makes the solution newly feasible
+- A market move that closes existing options
+
+Mike Maples Jr: "What do you know that's not obvious? Slide two of your pitch should be your earned secret." A presentation without an earned secret is a description. One with it is an argument.
+
+→ Deep dive: *Earned Secrets and Pitch Structure* — Mike Maples Jr, Giving Presentations
+
+### Write Story Points, Not Slides
+
+Open a notes app, not slide software. Write the narrative structure — what you're arguing and in what order — before touching any visual tool. Janna Bastow: "Now I figure out what I'm actually trying to say, and then I fit it into the deck." The deck should serve the story, not generate it.
+
+---
+
+## Part 2 — Story Structure
+
+### The Five Frameworks
+
+Choose based on `goal` and `audience`. The framework determines your spine.
+
+**Problem-Solution-Value (PSV)**
+For pitches where the audience already has the problem. Lead with the cost they feel, present the solution as the logical answer, prove it works, quantify the value.
+*Flow:* Problem → Solution → Evidence → Value → Call to Action
+
+**Before-After-Bridge (BAB)**
+For audiences who don't yet recognize they have a problem. Show the current state vividly, paint the desired future, reveal your product as the bridge.
+*Flow:* Current Reality → Desired Future → The Bridge → Evidence → Ask
+
+**Hero's Journey**
+For audiences going through disruption they did not choose. Cast them as the protagonist. You are the guide with the tool — not the hero.
+*Flow:* Status Quo → Disruption → Challenge → Guide (you) → Transformation → New Normal
+
+**Five-Whys**
+For internal or diagnostic presentations where understanding root cause matters more than selling. Each "why" is a spine node peeling back one causal layer.
+*Flow:* Observation → Why #1 → Why #2 → Root Cause → Solution
+
+**Minto Pyramid**
+For executive audiences who want the bottom line first. Lead with the recommendation, support with grouped arguments, provide evidence in drill-downs.
+*Flow:* Conclusion → Argument 1 → Argument 2 → Argument 3 → Next Steps
+
+→ Deep dive: *Strategic Narrative* — Andy Raskin; *Resonate* — Nancy Duarte
+
+### What Is vs. What Could Be
+
+The most persuasive presentations do not make their argument once — they alternate between the current flawed reality and the possible future, repeatedly widening the gap.
+
+1. Show the current state — the friction, cost, or limitation the audience recognizes
+2. Show what changes if the problem is solved — specific, concrete, desirable
+3. Repeat this cycle across the spine before the solution fully arrives
+4. Close with "new bliss" — the world after adoption, not just a product description
+
+Nancy Duarte: "This motion of traversing between what is and what could be makes people leave their current state and long for the future." The audience should feel the gap before they hear the answer. Understanding is not urgency; tension is.
+
+→ Deep dive: *Resonate* — Nancy Duarte; *What Is vs. What Could Be* — Nancy Duarte, Giving Presentations
+
+### The Audience Is the Hero
+
+You are Obi-Wan, not Luke. The customer is on a journey — your product is the lightsaber they need. Every slide should speak to "your situation," "your team," "your outcome." Do not make yourself the protagonist of your own presentation.
+
+Mike Maples Jr: "Describe the world that is, describe the world that could be — your job as the founder is to be Obi-Wan, not Luke."
+
+### Establish Stakes Immediately
+
+The audience must know what is at risk within 60 seconds. A problem slide without stakes creates intellectual interest, not urgency. Matthew Dicks calls this "the elephant" — something the audience is worried about from the first sentence.
+
+Do not ease in. Do not start with "Today I'm going to talk about..." Start in the middle of the problem at its most acute moment.
+
+Merci Grace: "Every pitch should start in the middle of the action. Skip the boring setup — hook them immediately."
+
+→ Deep dive: *Storyworthy* — Matthew Dicks
+
+### Spine Length and Drill-Down Logic
+
+The spine is the minimum viable presentation — it must tell a complete story on its own. Drill-downs are optional depth that skeptics and deep questioners can access without breaking the flow for everyone else.
+
+| Duration | Spine Nodes | Drill-Downs Per Node |
+|---|---|---|
+| 5–10 min | 4–5 | 0–1 |
+| 15–20 min | 5–6 | 1–2 |
+| 30+ min | 6–7 | 2–3 |
+
+Place objections in drill-downs, not the spine. Putting objections on the spine breaks momentum. Making them available via drill-down shows you anticipated the question without making the audience sit through an answer they may not need.
+
+---
+
+## Part 3 — Writing Each Slide
+
+### The One Thing
+
+Every slide has one key message. If you need "and" in the title, split the slide. If removing a bullet doesn't weaken the key message, remove it. If the audience cannot state what the slide was about in one sentence after it leaves the screen, it carried too much.
+
+### Assertion-Evidence Structure
+
+Replace bullet lists with assertion + evidence. The assertion is the headline — a specific claim. The evidence is visual proof: a chart, comparison, quote, or before/after. Evidence does not repeat the headline in text. It proves it.
+
+**Weak — assertion + more assertions:**
+> *Title:* The Problem
+> - Managing data is difficult
+> - Current tools are inefficient
+> - Teams waste time on manual processes
+
+**Strong — assertion + evidence:**
+> *Headline:* Mid-market finance teams lose 11 hours a week reconciling what three systems can't agree on
+> [Chart or role-by-role breakdown of where those hours go]
+
+→ Deep dive: *Assertion-Evidence Structure* — Michael Alley; *Presentation Design* — presentation-design skill
+
+### Headlines vs. Titles
+
+Titles label topics. Headlines make claims. The audience should understand your point from the title alone, without reading the body.
+
+| Title (label) | Headline (claim) |
+|---|---|
+| "Market Overview" | "The market shifted to outcome-based pricing in 2023" |
+| "Our Technology" | "One integration replaces three legacy systems" |
+| "Q3 Results" | "Q3 revenue exceeded forecast by 18%" |
+| "The Team" | "12 engineers with 200+ years of combined industrial experience" |
+
+Andy Raskin: "Every single slide should be a takeaway, not a label."
+
+### Spoken vs. Shown
+
+| Show on Slide | Speak Aloud |
+|---|---|
+| Headline claim | Why it matters to this specific audience |
+| Visual evidence | Interpretation — what the data means |
+| Specific numbers | The story behind the number |
+| Call to action | The stakes of not acting |
+
+The most common failure: slides containing everything the presenter plans to say. If the audience can read it, they will — and they'll tune out while you catch up. Slides are visual anchors for a spoken argument, not scripts.
+
+### Speaker Notes
+
+Notes should add what the presenter says aloud, not repeat what is on screen. Strong notes include:
+
+- The talking point the audience doesn't see
+- Which drill-down to navigate to if a specific objection arises
+- Audience-specific framing ("For technical audiences, emphasize...")
+- Time guidance ("Spend max 2 minutes here")
+- Transition language to the next slide
+
+### Framing Data
+
+A number without a frame is noise. A number with a frame is an argument.
+
+> ❌ "40% reduction"
+> ✓ "40% reduction — enough to pay back the installation cost in 14 months"
+
+Framing pattern: state the metric, then immediately state what it means for the audience. Use "enough to...", "which means...", "equivalent to...", or "compared to..." as connectors.
+
+### Chart Titles
+
+A chart's title states the insight, not the data category. The audience should understand your point before they read the chart.
+
+| Weak | Strong |
+|---|---|
+| "Revenue Data" | "Revenue grew 40% QoQ after the pricing change" |
+| "Response Time" | "Response time dropped 60% after caching rollout" |
+| "User Growth" | "1M users in 6 months — 2× ahead of plan" |
+
+---
+
+## Part 4 — Common Anti-Patterns
+
+**Bullet Point Disease**
+Slide after slide of lists, equal weight for unequal ideas, passive reading instead of active viewing. Fix: assertion-evidence. If you have a list, ask whether it should be a slide at all.
+
+**The Script Reader**
+Slides contain everything the presenter plans to say. Audiences read ahead, then tune out. Fix: slides show what you can't say; you say what you can't show.
+
+**The Data Dump**
+Every slide full of charts and statistics without interpretation or hierarchy. Audiences can't do analysis in real time. Fix: one insight per slide. State the conclusion; show the proof.
+
+**The Vague Opening**
+Starting with "Today I'm going to talk about...", an agenda slide, or a company overview before you've hooked anyone. Fix: start in the middle of the problem. Earn the agenda.
+
+**The Success Story**
+A presentation about how great things are, full of achievements and positive metrics. Audiences don't connect with success — they connect with problems and the path through them.
+Jason Feifer: "Success stories are not interesting. Problem-solving stories are."
+
+**The Franken-Deck**
+Trying to answer every possible objection from every possible skeptic in one presentation. Fix: put objections in drill-downs, not the spine. Mike Maples Jr: "Don't build a deck that tries to satisfy non-believers — it satisfies nobody."
+
+---
+
+## Part 5 — Delivery
+
+### Internalize, Don't Memorize
+
+Memorizing word-for-word creates catastrophic failure risk — lose your place once and the whole script collapses. Instead, internalize the structure:
+
+**The Accordion Method** (Tristan de Montebello): Practice the talk at a strict 3-minute limit. Then 1 minute. Then 30 seconds. At 30 seconds, you have the pure skeleton — the essential logic. Then expand back to full length. You now own the talk instead of reciting it.
+
+→ Deep dive: *Accordion Method* — Tristan de Montebello, Giving Presentations
+
+### State Changes
+
+Audience attention decays after 3–5 minutes of passive receiving. Build in a state change — a question, a data point to guess before revealing, a show of hands — every 3–5 slides. Make engagement a structural decision, not a personality trait.
+
+Wes Kao: "Every three to five slides, put in a state change. Turn audience engagement from an art into a science."
+
+### Stay in Character
+
+Do not apologize for minor verbal slips. Do not say "I'm nervous" or "I'm not sure this makes sense." Audiences rarely notice internal turbulence unless you leak it. Every apology signals uncertainty and invites doubt.
+
+The internal cue: "stay in it." Commit to the end of each sentence. Maintain energy through the last word. Land the plane.
+
+→ Deep dive: *Stay in Character* — Tristan de Montebello, Giving Presentations
+
+### Managing Nerves
+
+Anxiety and excitement share the same physiological response. Labeling the feeling as excitement rather than anxiety measurably improves performance.
+
+Matt Abrahams: "When you feel those symptoms of anxiety, say 'This is exciting. I get to share my point of view.' By seeing it as more positive, it causes us to relax."
+
+Breathing: exhale twice as long as you inhale (3 counts in, 6 counts out). The relaxation response is triggered by the exhale.
+
+98% of presentation nerves are pre-performance. Once you begin speaking, most of it falls away. The first sentence is the hardest. Prepare it cold.
+
+### Q&A
+
+Answer, then give an example, then state the relevance. Don't assume the audience knows why your answer matters — connect the dots explicitly.
+
+For difficult questions: "That's a valid concern. Here's how we thought about it." For out-of-scope questions: "Good question — let's take that offline." Never debug the problem in front of the room for more than 30 seconds. Have a "get out of jail" plan for any live demo or data pull that goes wrong.
+
+---
+
+## Quick Reference
+
+**Before building the deck:**
+1. Define the arrow (one sentence: what should they remember?)
+2. Name the earned secret (why is this urgent now?)
+3. Identify the audience's hero journey and the problem they face
+4. Write story points before touching slide software
+
+**Choosing a framework:**
+- Audience has the problem → **PSV**
+- Audience doesn't know they have the problem → **BAB**
+- Audience is navigating disruption → **Hero's Journey**
+- Audience needs to understand root cause → **Five-Whys**
+- Audience is time-pressed, wants bottom line first → **Minto Pyramid**
+
+**For every slide:**
+- State the one thing
+- Make the title a claim, not a label
+- Pair assertion with visual evidence, not more assertions
+- Put interpretation in speaker notes, not on screen
+
+**Delivery:**
+- Accordion method to internalize, not memorize
+- State change every 3–5 slides
+- Stay in character through the last word
+- Reframe anxiety as excitement
+
+---
+
+## Source References
+
+| Concept | Source |
+|---|---|
+| Bow and Arrow / The One Thing | Tristan de Montebello — *Giving Presentations* guest insights |
+| What Is vs. What Could Be | Nancy Duarte — *Resonate*; *Giving Presentations* guest insights |
+| Audience as Hero / Obi-Wan | Mike Maples Jr — *Giving Presentations* guest insights |
+| Earned Secret / Non-Obvious Insight | Mike Maples Jr — *Giving Presentations* guest insights |
+| The Elephant / Stakes Immediately | Matthew Dicks — *Storyworthy* |
+| Start in the Middle of Action | Merci Grace — *Giving Presentations* guest insights |
+| Make the Title the Takeaway | Andy Raskin — *Giving Presentations* guest insights |
+| Lead a Movement, Not Just Solve a Problem | Andy Raskin — *Brand Storytelling* guest insights |
+| Assertion-Evidence Structure | Michael Alley — *presentation-design* skill |
+| State Changes Every 3–5 Slides | Wes Kao — *Giving Presentations* guest insights |
+| Stay in Character | Tristan de Montebello — *Giving Presentations* guest insights |
+| Accordion Method | Tristan de Montebello — *Giving Presentations* guest insights |
+| Don't Memorize Word-for-Word | Paul Adams — *Giving Presentations* guest insights |
+| Problem-Solving > Success Stories | Jason Feifer — *Brand Storytelling* guest insights |
+| Memification | Yuhki Yamashata — *Brand Storytelling* guest insights |
+| Anxiety as Excitement | Matt Abrahams — *Giving Presentations* guest insights |
+| Chart Title = Insight Claim | *technical-presentations* slide design guide |
+| Franken-Deck Anti-Pattern | Mike Maples Jr — *Giving Presentations* guest insights |
+| Pre-Meetings to De-Risk | Casey Winters — *Giving Presentations* guest insights |