The ChatGPT prompts for presentations below take you from a blank page to a delivered talk: finding the one message, outlining the deck, writing slides and speaker notes, and rehearsing for questions. They work in ChatGPT, Claude and Gemini, and the last one turns your outline into an actual PowerPoint file.
How to use these prompts
Copy a prompt, replace the blanks in double braces, or keep the default after the colon: {{audience:the leadership team}} means "the leadership team" unless you change it.
Two habits do most of the work. First, tell the model who is in the room and what you want them to do afterward. A deck for a budget decision and a deck for a training session need different structures, and the model can't guess which one you need. Second, paste your real material: the report, the numbers, the notes. OpenAI's ChatGPT prompting guide suggests briefing the model like a capable new colleague: "Imagine you're assigning work to a smart intern on their first week."
Run the prompts in order for a new deck: message first, outline second, slides third. Fixing the message after the slides exist costs far more.
Which prompts help plan the talk?
1. Find the one message
Most weak presentations have no single point. Start here before you open any slide software.
I'm giving a {{length:15 minute}} presentation to {{audience:the leadership team}}.
Topic: {{topic}}
What I want them to do or decide afterward: {{goal}}
What they already know and care about: {{context}}
1. Write my main message in one sentence a listener could repeat later.
2. Give three supporting points that make the case, in the order that
persuades this audience best.
3. Name the objection this audience is most likely to raise, and where in
the talk I should answer it.
4. Tell me what to leave out.
2. Outline a deck from a document
Paste a report, a strategy doc or a page of notes. The one-message-per-slide rule stops the model from cramming.
Turn the material below into a slide outline for {{audience:the leadership team}}.
Target: {{slides:10}} slides.
For each slide give: a headline that states a conclusion (not a topic), the
two or three facts from the material that support it, and the visual that
would show it best (chart type, diagram, image, or text only). One message
per slide. Use only facts from the material. If the material is missing
something the story needs, list it at the end as a gap.
Material:
{{material}}
3. Storyline check from headlines only
A good deck makes sense if you read only the slide titles in order. This prompt tests that.
Here are the headlines of my slides in order. Read them as if they were the
whole presentation.
1. Does the story hold together? Where does it jump or repeat?
2. Which headlines are topics ("Q3 results") rather than conclusions
("Q3 revenue grew 12% on renewals")? Rewrite those.
3. Is the main message clear by the third slide?
4. Suggest a better order if there is one, and say why.
Headlines:
{{headlines}}
Which prompts write and fix slides?
4. Slide content with speaker notes
Once the outline is right, write each slide. Keeping detail in the notes keeps the slide readable.
Write the content for each slide in this outline.
For each slide:
- Headline: a full-sentence conclusion, under {{headline_words:12}} words.
- On-slide text: no more than {{max_bullets:3}} short lines, or a suggestion
for a chart or diagram instead of text.
- Speaker notes: what I say, in plain spoken language, about 30 to 60
seconds per slide.
Tone: {{tone:direct and confident, not salesy}}. Don't add facts that aren't
in the outline.
Outline:
{{outline}}
5. Rewrite a dense slide
For the slide with nine bullets and a paragraph. The output gives you options, since one dense slide often should become two.
This slide has too much on it. Here is everything on it now:
{{slide_text}}
The point of this slide is: {{point}}
Give me three options:
A. One slide: a conclusion headline and at most three short lines.
B. One slide with a visual instead of text: describe the visual exactly.
C. Split into two slides, with headlines for each.
For each option, move what I cut into speaker notes so nothing important is
lost.
6. Turn a table into a chart slide
Paste the numbers. The headline should say what the chart shows, so nobody has to work it out.
Here is a data table for a slide:
{{table}}
The audience is {{audience:the leadership team}} and the point I want to make
is {{point}}.
1. Recommend one chart type and say why it fits this point better than the
alternatives.
2. Write a headline that states the takeaway, with the key number.
3. Say what to highlight (one bar, one line, one cell) and what to gray out
or drop.
4. Check the numbers support my point. If they don't, or only partly do,
tell me plainly.
7. Executive summary slide
For decks that go to busy people who may read only the first slide.
Write an executive summary slide for the deck below. Someone who reads only
this slide should know: the situation, the main finding or proposal, what it
costs or changes, and what I'm asking for. Use at most five short lines and
a headline that states the ask. Then write a version for email, in five
sentences or fewer.
Deck outline or content:
{{deck}}
Which prompts help you deliver it?
8. Speaker notes to a timed script
Turns notes into words you can say out loud, with timing marks so you know if you're running long.
Turn these speaker notes into a script I can rehearse for a
{{length:15 minute}} talk. Write it the way people speak: short sentences,
contractions, no words I'd stumble over. Mark the expected time at the start
of each slide (for example [3:30]). Add a one-line transition between
slides. Flag any slide that will run long.
Notes:
{{notes}}
9. Prepare for hard questions
Ask for the questions you hope nobody asks. Answering them in advance is the difference between confident and defensive.
I'm presenting the deck below to {{audience:the leadership team}}. Their
priorities: {{priorities}}.
List the ten questions they are most likely to ask, starting with the
hardest. For each: why they'd ask it, a short answer I could give (using only
facts from the deck, and saying "I'd need to check" where the deck doesn't
support an answer), and whether I should add a backup slide for it.
Deck:
{{deck}}
10. Rehearsal feedback from a transcript
Record a practice run, transcribe it, and paste the transcript. Many recording and meeting tools can produce a transcript.
Here is a transcript of me rehearsing a {{length:15 minute}} presentation.
The intended main message is: {{message}}
Give me feedback on:
1. Whether the main message came through, and where.
2. Filler words and phrases I repeat, with counts.
3. Places where I over-explain or lose the thread.
4. The opening and closing: are they strong enough? Suggest a better
version of each in my own style.
Keep the feedback to the five changes that would help most.
Transcript:
{{transcript}}
11. Cut the talk to fit the time
For when your slot shrinks from 30 minutes to 10, which happens often.
My presentation was planned for {{old_length:30 minutes}} and now I have
{{new_length:10 minutes}}. Here is the outline with speaker notes.
Tell me which slides to keep, merge or move to an appendix, so the main
message survives. Keep the same opening and the same ask. Give the new
outline with timings, and list what the audience will no longer hear so I
can offer it as a follow-up.
{{outline}}
Which prompts fit common deck types?
12. Project update deck
For status reviews where the audience wants to know what changed and what you need from them.
Build a {{slides:5}} slide project update for {{audience:the steering group}}
from my notes below.
Slides: 1) status in one line with a clear on track, at risk or off track
call, 2) what was done since last update, 3) what's next with dates, 4)
risks and what we're doing about each, 5) decisions or help I need from this
group. Use plain language and no green-washing: if the notes show a slip,
say so.
Notes:
{{notes}}
13. Proposal deck for a decision
When you need a yes, a budget or a change in direction.
Outline a proposal deck asking {{audience:the leadership team}} to approve
{{proposal}}.
Structure it as: the problem and its cost today, options considered
(including doing nothing), the recommended option and why, cost and
timeline, risks and how we'd know early if it's failing, and the specific
decision I need today. For each slide, give a conclusion headline and the
evidence it needs. Mark any evidence I haven't provided with [NEED: ...].
What I have so far:
{{material}}
How do you turn the outline into a PowerPoint file?
ChatGPT is strong at the words; to get an actual file, you can paste its output into your slide tool or ask Claude to build it. Anthropic's help article on creating and editing files with Claude says "Claude can create Excel spreadsheets (.xlsx), PowerPoint presentations (.pptx), Word documents (.docx), and PDF files" when code execution and file creation is turned on in Settings > Capabilities (it is on by default for Free, Pro and Max plans). Anthropic also documents a Claude for PowerPoint add-in that builds and edits slides inside PowerPoint using your template, available on Pro, Max, Team and Enterprise plans. In Claude Code, the Claude PowerPoint skill teaches the agent to build and check .pptx files.
Use this prompt once your outline and slide content are final.
14. Build the .pptx from final content
Create a PowerPoint file (.pptx) from the slide content below.
- {{slides:10}} slides, 16:9.
- Put each headline in the slide title and the speaker notes in the notes
section, not on the slide.
- Use native, editable charts for any data, not images.
- Style: {{style:clean, white background, one accent color, large type}}.
- Keep on-slide text exactly as written; don't add new claims.
After creating it, check every slide for text that overflows or overlaps and
fix it before giving me the file.
Content:
{{content}}
Save the prompts you reuse
If you build the same kind of deck every month, turn prompt 12 into a skill with the SKILL.md generator so your agent applies the same structure each time. For investor decks, see the pitch and fundraising prompts in ChatGPT prompts for startups.
Kipt keeps prompts like these as Markdown in a private GitHub repo you own. Blanks such as {{audience}} and {{length}} stay fillable, so one prompt covers a board meeting and a team demo, and ⌘K brings it up when the next deck is due.