designing-presentationslisted

# Designing Presentations End-to-end content design for slide decks. Five sequential phases produce: an audience brief, a message architecture, a storyboard, per-slide drafts, and a critique report. The deliverable is a single `deck.md` file with YAML front-matter per slide. This skill stops at `deck.md`; rendering, styling, and presenting are the deck builder's job. ## When to Use Use this skill when the user wants to plan or refine the _content_ of a slide deck: who the audience is, what message moves them, how to order the slides, what each slide should say and show, what speaker notes back it up, and whether the result will land. Content design pays for itself before rendering: a storyline problem caught here costs one markdown edit, the same problem caught in a rendered deck costs a review round. Two entry modes: - **Design mode** (default): runs all five phases against a fresh idea. Output dir contains five named artifacts. - **Audit mode**: consumes an existing `deck.md` and runs only Phase 5 (heuristic audit plus three critic personas). Triggered when the user provides a path to an existing deck. ## Dependencies Nothing to install: filesystem operations only. The skill reads templates from its own `references/` directory and writes phase artifacts to the working directory. No external services, no APIs, no rendering. The one capability worth checking before Phase 5 is subagent dispatch (the Agent tool) for the three critic personas; when subagents are unavailab