12 AI Prompts for Creating a Presentation from Source Material

Useful AI prompts for creating presentations define the audience, outcome, authoritative sources, allowed interpretation, required evidence, presentation setting, and review standard. The 12 templates below cover the full workflow from source inventory to final PPTX quality assurance.

Replace the bracketed variables before using a prompt. Keep the original files, review every factual output, and treat the generated presentation as a draft until the exported artifact passes human review.

If you are editing an existing deck rather than creating a new one, use the separate library of AI prompts for editing PowerPoint.

The prompt contract for presentation creation

Microsoft's guidance for prompting includes goal, context, source, and expectations. See Write a great prompt in Microsoft 365 Copilot. For a presentation, add preservation rules and verification.

Use that contract consistently. A longer prompt is not automatically better; every line should reduce a real ambiguity.

Variables to prepare once

Fill in these values before using the templates:

• [AUDIENCE]
• [PRESENTATION OUTCOME]
• [DELIVERY SETTING]
• [TIME OR SLIDE RANGE]
• [AUTHORITATIVE SOURCES]
• [SOURCE CUTOFF DATE]
• [REQUIRED SECTIONS]
• [LOCKED FACTS]
• [BRAND RULES]
• [OUTPUT FORMAT]
• [REVIEW OWNERS]

If you cannot identify the source owner or cutoff date, the presentation may not be ready for generation.

1. Inventory the source material

Use this before outlining when you have several documents, spreadsheets, notes, or images.

Inventory the attached source material for a presentation. Do not create slides yet.

Presentation outcome: [PRESENTATION OUTCOME]
Audience: [AUDIENCE]
Source cutoff date: [SOURCE CUTOFF DATE]

For each source, report:
1. File name and apparent purpose.
2. Topics and evidence it can support.
3. Reporting period or version.
4. Conflicts, duplicates, or stale information.
5. Sensitive or uncertain content requiring owner review.
6. Presentation questions it cannot answer.

Create a source-of-truth table that identifies which file should control each fact category. Do not choose between conflicting values without an explicit rule. Flag the conflict and name the needed owner.

Checkpoint: Confirm the controlling source for metrics, product claims, dates, customer information, policy wording, and visual assets.

2. Build an audience and decision brief

Use this when the source is clear but the presentation job is still vague.

Create a presentation brief from the context below. Do not outline slides yet.

Audience role: [AUDIENCE]
What they already know: [KNOWN CONTEXT]
What they care about: [PRIORITIES]
Likely objections: [OBJECTIONS]
Required decision, action, or learning outcome: [PRESENTATION OUTCOME]
Delivery setting: [DELIVERY SETTING]
Available sources: [AUTHORITATIVE SOURCES]

Return:
1. One-sentence presentation purpose.
2. The audience's five most important questions in order.
3. Evidence needed to answer each question.
4. Content that should be excluded.
5. Risks if the presentation overstates the sources.
6. A concise creative and factual constraint list.

Distinguish supplied facts from your hypotheses about the audience.

Checkpoint: The presentation owner should approve the audience questions before the outline is created.

3. Find evidence gaps before generating slides

Use this to prevent AI from covering missing information with plausible wording.

Assess whether the approved source material can support the planned presentation.

Presentation outcome: [PRESENTATION OUTCOME]
Required sections: [REQUIRED SECTIONS]
Sources: [AUTHORITATIVE SOURCES]

For each required section, list:
- supported claims and exact source locations;
- partial evidence and its limitation;
- missing evidence;
- unresolved source conflicts;
- the owner who should resolve the gap;
- a safe neutral statement if the gap remains open.

Do not use general knowledge or web information unless I explicitly add it as an approved source. Do not infer a number, commitment, customer view, or causal relationship.

Checkpoint: Resolve critical gaps or keep them visible in the outline as open questions.

4. Generate a slide-by-slide outline

Use this only after the brief and source map are approved.

Create a slide-by-slide presentation outline.

Audience: [AUDIENCE]
Outcome: [PRESENTATION OUTCOME]
Delivery setting: [DELIVERY SETTING]
Time or slide range: [TIME OR SLIDE RANGE]
Sources: [AUTHORITATIVE SOURCES]
Required sections: [REQUIRED SECTIONS]
Locked facts: [LOCKED FACTS]

For every slide, provide:
1. Slide number.
2. One evidence-backed takeaway title.
3. The slide's single primary job.
4. Exact source evidence.
5. Recommended visual relationship or content form.
6. Speaker context that should not crowd the slide.
7. Unresolved question or review owner.

Do not design the slides. Do not add a claim without a source. Put detailed reference material in a proposed appendix.

Checkpoint: Read the titles alone. They should tell a coherent story and end with the intended action. Use the full AI presentation outline guide for the review process.

5. Stress-test the narrative

Use this after the first outline, before accepting it.

Audit this presentation outline without rewriting it.

Audience: [AUDIENCE]
Outcome: [PRESENTATION OUTCOME]
Source map: [SOURCE MAP]

Identify:
1. Slides that do not advance the audience's decision or learning path.
2. Duplicated claims or evidence.
3. Conclusions introduced before their support.
4. Missing transitions or unanswered audience questions.
5. Titles that overstate their evidence.
6. Slides trying to perform more than one primary job.
7. Appendix content incorrectly placed in the main story.

For every finding, cite the slide number and propose the smallest structural correction. Do not add new evidence.

Checkpoint: Require a reason for every added, removed, moved, split, or combined slide.

6. Create a constrained slide brief

Use this one slide at a time when the presentation matters.

Create a detailed brief for slide [SLIDE NUMBER].

Slide job: [SLIDE JOB]
Audience takeaway: [TAKEAWAY]
Source evidence: [SOURCE AND LOCATION]
Delivery setting: [DELIVERY SETTING]
Brand rules: [BRAND RULES]
Locked facts: [LOCKED FACTS]

Return:
1. Takeaway title under [MAXIMUM WORDS] words.
2. Essential body content within [SPACE OR WORD LIMIT].
3. Recommended visual relationship.
4. Mapping from every visible claim to its source.
5. Content for speaker notes or appendix.
6. Manual acceptance checklist.

Do not create a missing value, quote, example, label, icon meaning, or visual relationship. Preserve every unit, period, qualifier, and citation.

Checkpoint: A reviewer should be able to accept the slide based on the brief, not subjective preference.

7. Turn verified data into a chart slide

Use this only with an approved dataset and calculation rules.

Propose a chart slide from [DATA SOURCE, SHEET, AND RANGE].

Audience question: [QUESTION]
Approved takeaway: [TAKEAWAY]
Metric definitions: [DEFINITIONS]
Allowed calculations: [FORMULAS OR "none"]

Preserve every value, category, date, unit, denominator, and distinction between actual, target, forecast, and benchmark.

Return:
1. Recommended chart type and why it represents the relationship.
2. Takeaway title.
3. Required labels, legend, source, and qualification.
4. Source cells for each visible series.
5. Risks of misleading scale, aggregation, or causal interpretation.
6. An accessible alternative description.

Do not calculate a metric outside the approved formulas. Do not describe correlation as causation.

Checkpoint: Reconcile every plotted value with the source. The spreadsheet-to-PowerPoint workflow contains a full data QA process.

8. Convert dense text into a truthful visual structure

Use this when a source paragraph contains a real comparison, process, or hierarchy.

Turn the approved source text into one visual slide structure.

Source text: [SOURCE TEXT AND LOCATION]
Audience: [AUDIENCE]
Slide job: [SLIDE JOB]
Brand rules: [BRAND RULES]

First classify the source relationship as sequence, comparison, hierarchy, cause and effect, system, cycle, or another type. Explain which words in the source prove that relationship.

Then return:
1. Concise labels.
2. The visual structure and element mapping.
3. The reading order.
4. Details that move to notes or appendix.
5. Any relationship that remains ambiguous.

Do not add arrows, stages, causes, priorities, or dependencies that the source does not support. Keep objects editable where the presentation workflow supports it.

Checkpoint: Trace every visual element back to the approved source.

9. Draft speaker notes without inventing facts

Use this after the slide content is approved.

Draft speaker notes for slides [SLIDE RANGE].

Audience and setting: [AUDIENCE AND DELIVERY SETTING]
Total presentation time: [TIME]
Approved slides: [SLIDE CONTENT]
Approved sources: [AUTHORITATIVE SOURCES]

For each slide, provide:
- opening sentence;
- explanation of the visible evidence;
- one transition to the next slide;
- optional anticipated question;
- source reference.

Do not add a claim, anecdote, commitment, customer quote, or statistic that is absent from the approved sources. Do not repeat the slide text word for word. Flag any slide that lacks enough evidence to explain responsibly.

Checkpoint: Present the deck aloud. Notes should support delivery without becoming a second hidden narrative.

10. Create an executive summary slide

Use this after the body is stable, not at the beginning.

Create an executive summary from the approved presentation.

Audience: [AUDIENCE]
Required decision or action: [PRESENTATION OUTCOME]
Maximum content: [SPACE LIMIT]

Return:
1. One framing sentence.
2. The three most decision-relevant findings.
3. The recommended action, labeled as a recommendation.
4. The most material risk or condition.
5. The exact decision requested.

Every statement must already be supported in the presentation. Cite the slide number and source behind each point. Do not introduce new urgency, scope, results, or commitments.

Checkpoint: If a summary statement cannot point to supporting slides, remove or repair it.

11. Design the appendix plan

Use this to preserve evidence without crowding the main story.

Create an appendix plan for this presentation.

Main deck outline: [OUTLINE]
Sources: [AUTHORITATIVE SOURCES]
Likely audience questions: [QUESTIONS]

Recommend appendix slides for:
- source tables and metric definitions;
- methodology and sample limitations;
- detailed implementation steps;
- alternative options;
- risk detail;
- references and citations;
- backup examples.

For each appendix slide, state the audience question it answers and the source it uses. Do not move a material qualification or risk out of the main slide merely to make the presentation cleaner.

Checkpoint: The main story should remain honest without requiring the appendix to correct it.

12. Run final source, presentation, and PPTX QA

Use this after generation and editing.

Audit the final presentation against [AUTHORITATIVE SOURCES]. Do not make changes yet.

Audience and setting: [AUDIENCE AND DELIVERY SETTING]
Approved outline: [OUTLINE]
Locked facts and brand rules: [LOCKED FACTS AND BRAND RULES]
Required output: editable PPTX

Report findings in these sections:
1. Source accuracy: values, dates, units, names, citations, and qualifications.
2. Narrative: duplicated, missing, contradictory, or unsupported messages.
3. Visual communication: hierarchy, overflow, alignment, crops, charts, and tables.
4. Accessibility: titles, contrast, color-only meaning, alt text, links, and reading order.
5. PowerPoint handoff: fonts, objects, notes, links, media, layouts, and editability risks.

For every issue, include slide number, element, severity, evidence, and manual check. Distinguish confirmed defects from items the current environment cannot verify.

Do not mark the presentation as passed until the exported PPTX has been opened, edited, saved, reopened, and presented in PowerPoint.

Checkpoint: Use the complete presentation quality checklist for the final source, accessibility, privacy, and PPTX pass.

Use the prompts as review stages

Do not paste all 12 prompts into one request. Use them at the stage they control:

1. source preparation;
2. audience and evidence;
3. outline;
4. individual slide creation;
5. notes and appendix;
6. final QA.

When a result fails, name the failed condition. For example: "The title is concise but changes the reporting period" or "The chart is accurate but uses color as the only distinction." Correct that condition without reopening every approved decision.

Create the presentation in Yrkie

In Yrkie, start in Inventor mode with a prompt and supported source material. Review and refine the outline before slides are generated, then edit supported content in the canvas and export the finished deck to PPTX.

If you already have a useful PowerPoint, begin in Copyist mode and use the editing-specific prompt library instead of rebuilding the deck. Neither workflow removes the need to verify facts and inspect the exported file.

Start a presentation in Yrkie with Prompt 1 or Prompt 2, depending on whether your source pack or audience brief needs attention first.