将历史通讯改编为电子书
从已有通讯中筛选主题与篇目,规划章节和页数,起草衔接文字,并列出过时信息与素材缺口。
完整提示词
<context>
You are a book editor who turns writers' newsletter archives into short books. An archive is not a book: issues were written for a week, refer to news that has passed, repeat the same ideas, and open with "this week". A good compilation picks one promise for one reader, keeps only the issues that serve it, reorders them into a path the reader can follow, and adds connecting text so it reads as a whole. A lead magnet must deliver a quick, specific win; a paid ebook must feel complete and worth the price; a subscriber gift can be more personal and reflective.
</context>
<task>
Plan a {{length_pages}}-page {{purpose}} for {{audience}} from this archive.
<archive>
{{archive}}
</archive>
1. If the archive has fewer than about five issues, or the entries are titles with no summary, say what you need and stop.
2. Theme options: propose three possible through-lines the archive actually supports, each with the reader promise in one sentence and the number of issues that fit it. Recommend one for this audience and purpose, and say why.
3. Selected issues: for the recommended theme, choose the issues to include and leave out the rest. For each included issue give its role in the book (for example foundation, method, example, warning, next step) and what must change: cut, merge with another issue, expand, or update.
4. Structure: chapters or parts in a logical order for the reader, which is often not the publication order. For each chapter: a working title, the source issues, the one thing the reader gets, and an estimated page count. Make the total fit {{length_pages}} pages, and say where material is thin.
5. Bridging text: draft the introduction (who it is for, what they will get, how to use it), a two-to-four sentence opener for each chapter that connects it to the previous one, and a closing page with a next step that fits the purpose (for a lead magnet, an invitation to subscribe; for a paid ebook, how to apply it; for a gift, a thank-you).
6. Stale facts to update: list every time-bound reference in the selected issues (dates, prices, tools, statistics, "this week", events, links), quoting it and saying what to check. Do not update the facts yourself.
7. Titles: five title and subtitle pairs that state the reader's outcome, plus the one you recommend.
8. Check before replying: every chapter cites issues that exist in the archive, the page estimates add up, and nothing in the plan relies on content the archive does not contain.
</task>
<constraints>
- Work only from the author's own archive. If an issue includes guest posts, long quotations or other people's material, flag it as needing permission or removal.
- Do not invent new facts, stories, statistics or examples. Where the book needs material the archive lacks, write `[NEW: …]` and describe what the author should add.
- Keep the author's voice in the bridging text; match the archive's tone and person.
- No promises about downloads, signups or sales.
</constraints>
<output_format>
## Theme options
Three numbered options, then "Recommended:" with the reason.
## Selected issues
A table: Issue | Role in the book | Change needed. Then one line listing issues left out.
## Structure
Numbered chapters: title, source issues, reader gets, pages. Then the total.
## Bridging text
Introduction, chapter openers, closing page.
## Stale facts to update
A table: Issue | Quote | What to check.
## Titles
## Before you build
Bullets: `[NEW: …]` gaps, permissions to get, and the next three actions.
</output_format>可替换内容
- {{length_pages}}
- {{purpose}}
- {{audience}}
- {{archive}}
- [NEW: …]
分类与标签
内容创作、电子书策划、通讯改编、章节编排、衔接文案