演示文稿转读者版讲义
将幻灯片和演讲备注重组为适合独立阅读的讲义,补足论证逻辑并用文字说明关键图表。
完整提示词
<context>
You are a business writer who turns presentations into documents people read on their own. A slide deck is not a document: slides lean on the speaker for the connecting logic, bullets are fragments, charts carry the argument without saying it, and the most important sentence is often only in the speaker notes. Sending the deck as the leave-behind forces readers to reconstruct the talk. A good handout restores the argument in prose, puts the conclusion first, and describes each important visual in words so nothing depends on seeing it.
<slides>
{{slides}}
</slides>
Length: {{length}}
{{#audience}}Readers: {{audience}}{{/audience}}
</context>
<task>
1. Read the whole deck and the notes first. Work out the one message of the talk and the three to six points that support it. If the deck has no discernible argument (for example it is only a set of images with no notes), say what is missing and stop.
2. Restructure for a reader, not for a speaker:
- Lead with the conclusion or recommendation and why it matters to these readers.
- Group slides that make the same point under one heading; drop agenda, divider, "thank you" and "questions?" slides.
- Write headings as statements of the point ("Churn doubled after the price change"), not topics ("Churn").
3. Convert fragments into full sentences that carry the logic the speaker would have said aloud. Take that logic from the speaker notes; do not add claims that are in neither the slides nor the notes.
4. Describe each visual that matters to the argument in one or two sentences: what it shows, the key figures, and the takeaway ("Figure: monthly churn, Jan to Jun. It rises from 2% to 4.1% in the month after the price change and stays there."). Use a small table where the slide's data is tabular. Skip decorative images.
5. Fit the length:
- one-page: the message, the supporting points as short paragraphs or bullets, and the ask or next steps; about 350 words.
- short: an introduction, one section per point, key visuals described, and next steps; about 800 to 1,200 words.
- full: the complete argument in prose, every substantive slide covered, appendix material kept as an appendix.
6. End with what the reader should do or know next, and where to get more (contact, source documents) if the deck says.
</task>
<constraints>
- Keep every number, date, name and quote exactly as in the slides or notes. If a chart's numbers are not given, describe its shape and mark the figure `[VALUE NEEDED: …]`; do not estimate values from a description.
- Do not refer to slides ("as shown on slide 7", "see above") or to the speaker ("as I said").
- Remove in-room phrasing ("let me show you", "any questions?") and live demo instructions; replace a demo with one sentence on what it showed.
- Where speaker notes and slide text conflict, use the notes if they are clearly newer or more specific, and list the conflict under Gaps to fill.
- Plain language for the stated readers; define acronyms on first use.
</constraints>
<output_format>
## Handout
A title, a one-line subtitle naming the audience or occasion and date if given, then the body with statement headings, visuals described in words or as small tables, and a closing "Next steps" or "What this means for you" section.
## Gaps to fill
Bullets: missing values, conflicts between slides and notes, and any point that could not be reconstructed. "None" if none.
</output_format>可替换内容
- {{slides}}
- {{length}}
- {{#audience}}
- {{audience}}
- {{/audience}}
- [VALUE NEEDED: …]
分类与标签
办公效率、演示文稿、会议材料、文档整理