Turn a document into slides
Turns a document or report into a slide outline with one message per slide, action titles that tell the story, suggested visuals from the document's own data, and an appendix plan.
A document and a deck do different jobs. A document is read at the reader's pace and can hold every detail; a deck is a sequence of single messages, usually seen while someone talks, and often skimmed later by title alone. Converting one into the other fails when each document section becomes a slide of shrunken paragraphs, when titles are topic labels ("Methodology", "Results") instead of the point, and when every finding gets equal weight. The working method is to find the document's governing message, rebuild the argument as a sequence of action titles that tell the story when read alone, give each slide one piece of evidence, and push supporting detail to an appendix.
Turn this document into a slide outline. Only if [AUDIENCE] is given: Audience and goal: Only if [SLIDE_COUNT] is given: Target: main slides.
- If the document is too short or fragmentary to present, say so and ask what the presentation should achieve; then stop.
- State the governing message in one sentence: what the audience should conclude. If no audience was given, assume the document's own intended reader and say so.
- Choose the storyline order for this audience: answer first for executives and decision-makers; context, then findings, then implications for less familiar audiences. Explain the choice in one line.
- Write the action titles first: one full-sentence takeaway per slide, ideally under 15 words, so that reading only the titles tells the whole story. If no slide count was given, propose one that fits the content (often 8 to 15 for a 20-minute slot) and say why.
- For each slide, specify: the single supporting element (a chart type with what to plot from the document's data, a diagram, a short table, an image, or up to three bullets of at most 10 words each), the source section of the document, and one line of what the speaker would say.
- Plan the appendix: detail, methodology, full tables and caveats that someone may ask about, each with the main slide it supports.
- List what you left out of the main flow and why.
- Use only content from the document. Do not invent data, examples or conclusions, and do not round or change numbers. If a visual would need data the document lacks, say so in Gaps.
- One message per slide. If a slide needs two, split it.
- Keep caveats and limitations that change the meaning of a finding on the main slide, not only in the appendix.
- Chart choices must suit the data: comparisons as bars, change over time as lines, parts of a whole only when they truly sum to 100%.
- No decorative slides (agenda, "thank you", "questions?") unless the audience or format requires them; mention them in one line if so.
Storyline
Governing message, chosen order and why, and the titles alone as a numbered list.
Slides
For each: N. Action title; Visual or content; Source (document section); Say (one line).
Appendix
Numbered: A1, A2… title, content, supports slide N.
Left out
Bullets with reasons.
Gaps
Data or material the deck needs that the document does not supply. "None" if none.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Presentations
- level
- Intermediate
- made for
- Consultant / freelancer, People manager, Researcher / scientist, Business analyst
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install turn-document-into-slides --target claude-codenpx skills add hermes-hq/hodios-dist --skill turn-document-into-slides -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of PresentationsOutline a presentation
Outlines a story-driven presentation with assertion-style slide titles, using SCQA or the pyramid principle, sized to the time slot and aimed at a stated goal for a specific audience.
outline-presentationWrite speaker notes
Writes natural, speakable notes for each slide with a time budget, the one point to stress and a transition to the next slide, and checks the total fits the time slot.
write-speaker-notesCritique a slide deck
Critiques a slide deck for storyline, one idea per slide, text density and visual clarity, and returns ranked slide-level fixes with rewritten titles. Use before presenting or sending a deck.
critique-slide-deckWrite an executive summary
Writes an executive summary of a long document that leads with the bottom line, the key points and the ask, using only facts from the source. Use before sending a report to busy readers.
write-executive-summaryPlan slide visuals
Proposes the visual for each slide in an outline, whether a chart type, diagram, image or none, with layout notes and data needs, so a deck shows its points rather than telling them.
plan-slide-visualsPresentation track
Takes a presentation from audience and goal to storyline, slide content, speaker notes and a rehearsal with likely questions, pausing for approval between steps.
presentation-track