# Weekly Summary Workflow Prompt You Run Yourself

> A reusable chat prompt that helps you plan a manual weekly-summary workflow: source table, retrieval order, review checks and missed-week handling.

## Install

Copy the content below into your project:

# Weekly Summary Workflow Prompt You Run Yourself

A reusable chat prompt that helps you plan a manual weekly-summary workflow: source table, retrieval order, review checks and missed-week handling.

## Start here

This is a plain-text prompt for an ordinary AI chat that accepts text. You do not need a terminal, API, account setup or any add-on.

**What to paste.** First paste this original prompt, then paste your own short list: the summary's goal and readers, the places the week's material lives (notes app, shared doc, chat thread, spreadsheet, folder), the exact start and end dates, the section order you want, any recurring callouts, length and tone limits, and last week's summary if you have one. Write MISSING for anything you don't have.

**Where to paste.** Into any general chat assistant that can read pasted text. Keep it in one conversation so the assistant can refer back.

**How to check the output.** The reply should contain a source table where every source has a concrete manual retrieval step, a numbered retrieval checklist, one copyable weekly prompt block, file-name guidance, 6-10 pass/fail review checks, missed-week steps and a short boundaries list. If a source has no manual retrieval path, it should be flagged and stopped, not guessed. The weekly prompt inside the reply must require a source label on every claim, mark single-source items as SINGLE-SOURCE and unclear ones as UNCLEAR.

## What this is for

Weekly summaries fail when the person writing them expects software to collect, schedule or send the material. This prompt removes that assumption. It only produces two things: a plan you can carry out by hand, and a reusable prompt you paste each week with the week's material underneath.

Note the word *fictional* in the prompt's example. It only shows the expected shape; the numbers and outcomes in it are not test results. Source reviewed; runtime not tested.

## What you get back

| Block | Purpose |
| --- | --- |
| Setup | Sources table plus a numbered retrieval checklist |
| Reusable weekly prompt | One self-contained plain-text block to copy |
| Keep and name | What to keep after each run and how to name files |
| Review checklist | 6-10 pass/fail checks tied to your goal |
| If I miss a week | How to extend the window and label the gap |
| Boundaries | What the workflow does not do |

## Permissions and limits

- The plan is executed by you: every export, copy and send is a manual action.
- Nothing here schedules, watches files, sends messages or remembers previous weeks.
- If the goal, sources or time window are missing, the assistant should ask before writing the prompt. Style-only gaps are labelled as assumptions.
- Do not paste confidential material into the chat unless the provider's terms and your own confidentiality limits allow it. Redact names, figures or client details first.
- Treat the drafted summary as a draft: you check the quotes, numbers and labels before sharing.

## FAQ

**Do I need an app or automation tool?** No. The whole point is that the workflow runs through your own hands. The prompt explicitly forbids claiming that any tool can watch, schedule or send for you.

**Can it recover a week I skipped?** It gives numbered steps: extend the window, label the gap, and keep two weeks from being merged into one. You still copy the material yourself.

## Source and thanks

Original TokRepo prompt, category: everyday agents, task: plan a recurring weekly-summary workflow without pretending a schedule exists. Licensed CC BY 4.0; external reference material keeps its own rights. Reference: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>) (reviewed 2026-10-04), noted only as context for the evolving general-purpose AI workspace. The complete original prompt and its full Chinese translation are appended by the publisher.

## Complete reusable prompt

You are helping me design a recurring weekly-summary workflow that I will run myself. Do not assume any tool can schedule itself, watch my files, send messages, or remember last week. I will supply the inputs; you only produce a plan and a reusable prompt I can paste into a chat later.

INPUTS I WILL PROVIDE (paste what you have; write MISSING for the rest)
1. Goal: what the weekly summary is for, who reads it, and what decision or action it supports.
2. Sources: the places the week's material lives (for example a notes app, a folder of meeting notes, a spreadsheet, an inbox label, a chat thread, a shared doc). For each source, say how I get its content out by hand or by export.
3. Time window: the exact start and end, plus the day I will assemble it.
4. Sections I want in the summary and their order.
5. Known recurring items (callouts that appear most weeks).
6. Constraints: length, tone, anything that must never appear, confidentiality limits.
7. Last week's summary, if one exists, so you can match its shape.

WHAT TO DO
Step 1 - Sources check. Build a table: Source | How I retrieve it | Format it arrives in | Anything I must do first (e.g. export, rename, copy). If any source has no manual retrieval path, flag it and propose a substitute, then stop that source rather than guessing.
Step 2 - Assembly order. Give me a numbered retrieval checklist in the order I should copy or export material, with a one-line purpose for each step. Keep it to the minimum that satisfies the goal.
Step 3 - Reusable summary prompt. Write me one self-contained prompt I can paste into a chat each week, with the pasted material underneath. That prompt must: state the section order; require every claim to carry the source label I supplied; mark any item that appears in only one source as SINGLE-SOURCE; mark anything unclear as UNCLEAR rather than filling it in; keep to my length and tone limits; and end with a short list of open questions for me.
Step 4 - Draft pack. Tell me what to keep after each run (the pasted inputs, the drafted summary, my edits) and how to name files so a later week can be compared without re-reading everything.
Step 5 - Weekly review checklist. Give me 6-10 pass/fail checks I run on the drafted summary before I send or share it, tied to my stated goal and sources, not generic advice.
Step 6 - Missed week. Describe what happens if I skip a week: how to extend the window, how to label the gap, and how to avoid presenting two weeks as one.
Step 7 - Boundaries. State plainly what this workflow does NOT do: it does not schedule, monitor, send, or remember anything by itself; all retrieval and any sending is my manual action.

OUTPUT FORMAT
- 'Setup' with the sources table and the retrieval checklist.
- 'Reusable weekly prompt' as one clearly delimited block of plain text I can copy.
- 'Keep and name' short bullet list.
- 'Review checklist' as checkbox items.
- 'If I miss a week' short numbered steps.
- 'Boundaries' three to five bullets.

MISSING-INPUT RULE
If goal, sources, or time window is missing, ask me for them before producing the prompt. If only style details are missing, proceed and label your assumption clearly at the top.

FICTIONAL EXAMPLE (for shape only)
Input: Goal - a short Friday recap for a three-person study group. Sources - our shared notes doc and a group chat. Window - Monday to Friday. Sections - done, blocked, next week, questions.
Expected shape: the retrieval checklist says 'open notes doc, copy the week's headings'; the reusable prompt returns four sections, each line labelled with its source, blocked items flagged UNCLEAR where the chat and notes disagree, and two open questions at the end.

CHECKS BEFORE YOU HAND ME THE RESULT
- Does every source in my list have a concrete manual retrieval step?
- Does the reusable prompt require source labels on every claim?
- Does it flag one-source and unclear items instead of smoothing them over?
- Is the whole plan runnable by me alone, with no assumed automatic scheduling or sending?
- If last week's summary was supplied, does the shape match it?

BOUNDARIES
Keep to my supplied material. Do not invent sources, numbers, or recurring items. Do not claim any tool can watch, schedule, or send for me. Preparing the plan and the draft prompt is not the same as running or sending the summary; that part stays manual.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 由你自己执行的每周总结工作流提示词

一套可复用的对话提示词，帮你规划纯手动的每周总结流程：来源清单、收集顺序、复核清单与漏周处理方式。

## 开始使用

这是一段纯文本提示词，用在任何能接收文本的普通 AI 对话里即可。不需要终端、接口、账号配置或任何插件。

**需要粘贴什么。** 先粘贴这份原始提示词，再粘贴你自己的简短清单：总结的用途与读者、这一周材料存放的位置（笔记应用、共享文档、聊天记录、表格、文件夹）、准确的起始与结束日期、你想要的栏目顺序、每周都会出现的固定事项、篇幅与语气限制，以及上周的总结（如果有）。没有的信息就写 MISSING。

**粘贴到哪里。** 粘贴到任何能读取文本的通用对话助手中。尽量保持同一个对话，方便它回看前文。

**怎么检查结果。** 回复中应当包含：一张来源表（每个来源都有明确的手工获取步骤）、编号的收集清单、一段可直接复制的每周提示词、文件命名建议、6-10 条通过/不通过复核项、漏周处理步骤，以及一段简短边界说明。如果某个来源没有手工获取路径，它应被标出并停用，而不是靠猜测补全。回复中的每周提示词必须要求每条内容都带来源标签，把单一来源的条目标为 SINGLE-SOURCE，把不清楚的标为 UNCLEAR。

## 这份提示词解决什么问题

每周总结最容易出问题的地方，是写的人以为软件会自动收集、定时或发送材料。这份提示词去掉了这个假设。它只产出两样东西：一份你能亲手执行的计划，以及一段每周复制、末尾附上本周材料的可复用提示词。

注意提示词示例中标明了「虚构」。它只展示预期形态，其中的数字与结果不是测试结果。已审阅来源；未做运行测试。

## 你会得到的内容

| 区块 | 作用 |
| --- | --- |
| Setup | 来源表 + 编号的收集清单 |
| Reusable weekly prompt | 一段可复制的纯文本提示词 |
| Keep and name | 每次运行后保留什么、如何命名文件 |
| Review checklist | 6-10 条与你的目标挂钩的通过/不通过检查 |
| If I miss a week | 如何延长窗口、标注空档 |
| Boundaries | 这个流程做不到什么 |

## 使用权限与限制

- 计划由你自己执行：每次导出、复制、发送都是手工动作。
- 这里没有任何定时、监视文件、发送消息或记住上周内容的能力。
- 如果目标、来源或时间窗口缺失，助手应先向你索取，再写提示词。只缺风格细节时，应在开头标明这是假设。
- 除非服务条款和你自己的保密要求允许，不要粘贴机密材料。先抹去姓名、数字和客户信息。
- 把生成的总结当作草稿：分享前你自己核对引文、数字与标签。

## 常见问题

**需要额外的应用或自动化工具吗？** 不需要。这个流程的重点就是由你亲手完成。提示词明确禁止声称任何工具能替你监视、定时或发送。

**漏掉一周怎么办？** 它会给出编号步骤：延长窗口、标注空档，并避免把两周混成一周。材料仍需你自己复制。

## 来源与致谢

TokRepo 原创提示词，类别：日常智能体，任务：规划一套每周总结流程，且不假装存在定时能力。采用 CC BY 4.0 许可；外部引用材料保留其自身权利。参考资料：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)（2026-10-04 查阅），仅作为通用 AI 工作空间持续演进的背景说明。完整原始提示词及完整中文译文由发布方附上。

## 完整可复制提示词

你正在帮我设计一套每周重复执行的总结工作流，由我自己运行。不要假设任何工具能自行定时、监视我的文件、发送消息或记住上周内容。输入由我提供；你只产出一份计划，以及一段我之后可以粘贴进对话的可复用提示词。

我将提供的输入（有什么就粘贴什么；其余写 MISSING）
1. 目标：这份每周总结是做什么用的、谁读它、它支持什么决策或行动。
2. 来源：这一周材料存放的位置（例如笔记应用、会议记录文件夹、表格、收件箱标签、聊天记录、共享文档）。对每个来源，说明我如何手工或通过导出获取其内容。
3. 时间窗口：准确的起始与结束日期，以及我将在哪天进行汇总。
4. 我希望总结包含的栏目及其顺序。
5. 已知的周期性事项（大多数周都会出现的固定内容）。
6. 限制：篇幅、语气、绝不能出现的内容、保密限制。
7. 上周的总结（如果有），以便你匹配它的形态。

需要做什么
第 1 步 - 来源检查。建一张表：来源 | 我如何获取 | 送达时的格式 | 我必须先做的事（例如导出、重命名、复制）。如果任何来源没有手工获取路径，标出它并提出替代方案，然后停用该来源，而不是靠猜测补全。
第 2 步 - 汇总顺序。给我一份编号的收集清单，按我应当复制或导出材料的顺序排列，每一步附一句用途说明。只保留满足目标所需的最少步骤。
第 3 步 - 可复用的总结提示词。给我写一段自包含的提示词，我可以每周粘贴进对话，并在下方附上粘贴的材料。该提示词必须：说明栏目顺序；要求每条内容都带上我提供的来源标签；把只出现在一个来源中的条目标为 SINGLE-SOURCE；把任何不清楚的内容标为 UNCLEAR，而不是替它补全；遵守我的篇幅与语气限制；并以一份给我的简短待解决问题清单结尾。
第 4 步 - 草稿包。告诉我每次运行后要保留什么（粘贴的输入、起草的总结、我的修改），以及如何命名文件，以便之后某一周无需重读全部内容就能进行比较。
第 5 步 - 每周复核清单。给我 6-10 条通过/不通过检查，供我在发送或分享前对起草的总结执行，且要与我说过的目标与来源挂钩，而不是泛泛的建议。
第 6 步 - 漏周。说明如果我跳过一周会怎样：如何延长窗口、如何标注空档，以及如何避免把两周当成一周呈现。
第 7 步 - 边界。清楚说明这套工作流不做什么：它本身不定时、不监视、不发送、也不记住任何内容；所有获取和任何发送都是我自己的手工动作。

输出格式
- 'Setup'，含来源表和收集清单。
- 'Reusable weekly prompt'，作为一段清晰界定的纯文本，供我复制。
- 'Keep and name'，简短的项目符号列表。
- 'Review checklist'，作为复选框条目。
- 'If I miss a week'，简短的编号步骤。
- 'Boundaries'，三到五个项目符号。

缺失输入规则
如果目标、来源或时间窗口缺失，先向我要这些信息，再产出提示词。如果只缺风格细节，继续执行，并在开头清楚标明你的假设。

虚构示例（仅展示形态）
输入：目标——为一个三人的学习小组写一份简短的周五回顾。来源——我们的共享笔记文档和一个群聊。窗口——周一至周五。栏目——已完成、受阻、下周、问题。
预期形态：收集清单写「打开笔记文档，复制本周的标题」；可复用提示词返回四个栏目，每行都标有来源，聊天与笔记不一致的受阻条目标为 UNCLEAR，结尾有两个待解决问题。

你交给我结果前的校验
- 我列出的每个来源是否都有明确的手工获取步骤？
- 可复用提示词是否要求每条内容都带来源标签？
- 它是否会把单一来源和不清楚的条目标出，而不是含糊带过？
- 整个计划是否只靠我自己就能运行，不假设任何自动定时或发送？
- 如果提供了上周的总结，形态是否与它一致？

边界
只使用我提供的材料。不要编造来源、数字或每周固定事项。不要声称任何工具能替我监视、定时或发送。准备计划和草拟提示词不等于运行或发送总结；那部分仍需手工完成。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/weekly-summary-workflow-prompt-you-run-yourself-edacc17d
Author: Prompt Lab