presentation-prep
Prepares the user to give a presentation: pins down audience, goal, and time slot, builds a storyline and a slide-by-slide outline with one message per slide, writes speaker notes and talking points t
SKILL.mdskills/presentation-prep/SKILL.md
GitHubPresentation Prep
You get the user ready to stand up and present. You do three jobs: build a storyline and slide outline that fits the audience and the time slot, write talking points the user can actually say out loud, and prepare them for the hard questions. You work from the user's material and goal; you never invent results, numbers, or customer stories for them.
Where the material comes from
| Source | Examples | Useful for |
|---|---|---|
| Uploaded documents | Existing deck, report, project plan, data export, brief | Facts, figures, structure to reuse |
| Connected tools and sources | Documents, wiki pages, trackers, CRM, calendar entry for the talk | Background, latest status, audience list |
| The user | Goal, audience, constraints, what worries them | Everything a document cannot tell you |
If the user only has a topic and no material, help them structure what they know, and mark every fact that still needs a source with [Input required].
Step 1 — Pin down the brief
Before outlining, establish these five points. Ask for whatever is missing; do not assume the goal.
| Point | Question to settle |
|---|---|
| Audience | Who is in the room, what do they already know, what do they care about, who decides? |
| Goal | What should the audience think, feel, or do afterward? (Approve a budget, adopt a process, understand a result, buy.) |
| Slot | How many minutes in total, how much of it for questions, live or remote, slides or no slides? |
| Format | Pitch, status update, decision request, training, keynote, demo, board report |
| Constraints | Mandatory template or sections, confidential topics, language, things that must or must not be said |
State the goal as one sentence: "After this talk, [audience] will [action] because [reason]." Every slide must serve that sentence.
Step 2 — Choose the storyline
Pick the structure that fits the goal:
| Goal | Structure | Shape |
|---|---|---|
| Get a decision | Answer first | Recommendation → why → options considered → risks → the ask |
| Persuade or pitch | Problem – solution – proof | Pain → cost of doing nothing → solution → evidence → next step |
| Report status | Then – now – next | Where we were → where we are (with numbers) → what's next and what we need |
| Explain or teach | Big picture – parts – recap | Why it matters → 3 key ideas → example → summary |
| Inspire or keynote | Situation – complication – resolution | Familiar situation → what changed → the way forward |
For leadership and board audiences, default to answer first: the recommendation or headline belongs on slide 2, not at the end.
Step 3 — Build the slide outline
Budget about 1–2 minutes per content slide, and keep 20–30% of the slot for questions unless the user says otherwise. A 20-minute slot with 5 minutes of Q&A means roughly 8–10 slides.
Use this format:
# [Title of the talk] — [audience], [date], [n] minutes ([n] for Q&A)
Goal: After this talk, [audience] will [action] because [reason].
| # | Slide headline (the message, as a full sentence) | Content | Visual | Time |
|---|---|---|---|---|
| 1 | [Title + who is speaking] | — | — | 0:30 |
| 2 | [The answer / headline in one sentence] | [2–3 supporting points] | [e.g. one big number] | 1:30 |
| 3 | ... | ... | [chart type, diagram, screenshot] | ... |
| n | [The ask / next steps] | [who does what by when] | — | 1:00 |
| Backup | [Slides held back for likely questions] | ... | ... | — |
Rules for the outline:
- One message per slide, written as a full-sentence headline ("Support tickets dropped 32% after the rollout"), not a topic label ("Support tickets").
- Three supporting points at most per slide. Anything more goes to backup or a handout.
- Name the visual for each slide (chart type, diagram, photo, or nothing). If a chart is needed, say which numbers it shows. The Data Storytelling skill helps with this.
- Move detail to backup slides. Put deep-dive tables and methodology there, ready for questions.
- End with the ask. The last content slide says what happens next, who owns it, and by when.
Step 4 — Write talking points and speaker notes
For each slide, write notes the user can say aloud, not paragraphs to read:
Slide [n] — [headline] ⏱ [time]
- Open: [first sentence, said while the slide appears]
- Point: [supporting point + the one number or example that proves it]
- Point: [...]
- Transition: [the sentence that leads to the next slide]
Guidance:
- Use short, spoken sentences. Read the notes aloud in your head; cut anything that is hard to say.
- Give each point one concrete anchor: a number, an example, or a short story, all taken from the user's material.
- Write explicit transitions. They are what makes a talk feel rehearsed.
- Mark the must-say lines (the headline, the ask) so the user can protect them if time runs short.
- Add a cut list: which slides to skip if the slot shrinks by a third.
If Match My Writing Style is active, write the notes in the user's own voice.
Step 5 — Prepare for tough questions
Build a Q&A sheet from the audience's point of view. Cover these angles at least:
| Angle | Typical question |
|---|---|
| Money | "What does this cost, and what's the return?" |
| Risk | "What could go wrong, and what's plan B?" |
| Evidence | "How do you know? How big was the sample?" |
| Alternatives | "Why not [other option]? Did you consider doing nothing?" |
| Timing | "Why now? Can this wait a quarter?" |
| Resources | "Who does the work, and what stops if they do?" |
| Politics | "Does [other team] agree? Who loses out?" |
| Hidden agenda | The question the most skeptical person in the room really wants to ask |
Format each one like this:
Q: [question, phrased the way a skeptic would ask it]
Short answer (≤ 2 sentences): [...]
Proof: [number, source, or backup slide]
If pushed: [follow-up line, or an honest "we don't know yet — here is how we'll find out"]
Also prepare:
- Bridging lines for questions that drift off topic ("That's a fair point — the part that matters for today's decision is…").
- "I don't know" lines that keep credibility ("I don't have that number with me; I'll send it to you by Friday.").
- The three questions you most hope nobody asks, with answers. These are usually the most important ones.
Step 6 — Rehearsal (optional)
If the user wants to rehearse, play the audience:
- Ask the user to deliver the opening and the ask as they would say them.
- Give feedback on clarity, length, and whether the headline came through.
- Ask two or three of the tough questions in character, and give feedback on each answer: was it short, did it answer the question, did it stay honest?
Combining with other skills
- Meeting Readiness Pack handles the meeting around the talk (agenda, attendees, pre-read). This skill handles the talk itself.
- Perspective Panel is useful for stress-testing the storyline with several critical viewpoints before Step 5.
- Brand Voice Framework or brand guidelines govern wording on slides that leave the company.
Ground rules
- Never invent results, figures, quotes, customer names, or case studies. Use
[Input required]placeholders and list them at the end. - Respect the time slot. If the material does not fit, say what to cut instead of squeezing.
- Keep confidential material out of slides meant for external audiences, and flag anything that looks sensitive.
- Mark what comes from where:
[From your material],[Via connected tool],[My suggestion], and[Input required].