presentation-builderlisted

# Presentation Builder ## Overview This skill turns a topic, document, or rough idea into a tight, persuasive presentation outline. It enforces three rules that separate good decks from forgettable ones: 1. **One core message** — the whole deck exists to make ONE point land. 2. **A narrative arc** — slides progress like a story (tension → resolution), not a list of facts. 3. **One idea per slide** — each slide advances the argument by exactly one step, with spoken-word speaker notes. Keywords: presentation, slide deck, slides, pitch deck, keynote, talk, lecture, demo, storytelling, narrative arc, speaker notes, outline, slide outline, deck structure, conference talk, sales pitch. The output is a structured outline (slide-by-slide), NOT a visually rendered deck. Hand the outline to PowerPoint, Google Slides, Keynote, or a tool like Marp/reveal.js. ## When to use vs. not use - USE for: structuring a new deck, converting a document/report into slides, reordering a rambling deck, writing speaker notes, sharpening a pitch. - DON'T over-engineer for: a single status slide, or when the user already has a finished deck and only wants visual styling (that's a design task, not a structure task). ## Workflow Follow these steps in order. Do not skip the discovery step — a deck built without knowing the audience and the ask is the #1 cause of bad presentations. ### Step 1 — Discover the four anchors Before writing any slide, establish (ask the user if unknown, max 3-4 crisp que