你是一位资深的技术团队负责人，擅长把零散的工作素材整理成

有信息量的周报。

我的素材（原始记录，可能杂乱）

【在这里粘贴你一周的原始记录：commit说明、会议要点、

聊天片段、踩坑记录，格式不限】

读者与目的

这份周报的读者是【老板 / 协作方 / 项目组】，TA最关心的是：

1. 关键进展是否按计划推进
2. 有没有风险和阻塞需要TA知道或决策
3. 下周的预期是否明确

任务

1. 从素材中提炼出 3-5 条主线工作，合并碎片化的同类项，

不要逐条罗列

1. 每条主线用「做了什么 → 带来什么价值/消除了什么风险」

的结构表述，价值要具体、可核查，不许夸大

1. 单独列出「风险与阻塞」：凡是被推迟、在等待外部、

存在不确定的事项，说明影响和建议的解决方式

1. 单独列出「需要读者决策/协助的事项」
2. 基于本周遗留项，生成下周计划（3条以内，可执行）
3. 把模糊表述（"差不多""应该快了"）改写为具体说法，

素材中没有依据的信息不要编造，标注[待补充]即可

输出格式

本周进展

风险与阻塞

需要决策/协助

下周计划

Item 6 in the template is the key to preventing hallucinations—explicitly telling the AI "if there's no basis, mark it as [to be filled in]" saves far more hassle than discovering afterward that it fabricated a number.

## Before and After Using AI

**Before (manual version, ~40 minutes):** Starting Friday afternoon, racking your memory about what you did this week, digging through chat logs, writing "Monday fixed the login bug, Tuesday had meetings, Wednesday wrote code..." You send it out feeling uneasy, because even you can't articulate what this week's core output was. When the boss follows up with "how much impact did that bug have?" you freeze on the spot.

**After (AI-assisted version, ~10 minutes):** The material has been accumulated along the way; Friday you spend 5 minutes running the prompt, and AI produces a structure of main threads + value + risks, then you spend another 5 minutes calibrating facts and tone. The report goes out with a built-in "Risks and Blockers" section—once, AI dug up from my notes "waiting on third-party API docs for three days now," something I'd almost forgotten about myself. I listed it as a blocker, and my boss pushed the other party that same day. **The weekly report went from "reporting obligation" to "a tool for securing resources"—that's the biggest difference.**

## A Few Tips on Tool Selection

This workflow isn't picky about models, but different steps demand different capabilities: for material consolidation and formatting, a lightweight model is enough; value translation and risk identification require stronger comprehension and are worth running on a better model. If you switch between multiple models, going through a unified gateway is far more convenient than configuring each tool separately—for pricing, refer to the official pricing page.

If you want to try it hands-on, start by registering an account with a multi-model service, save the prompt template above, and run it with your real material this Friday—compare the output with last week's report, and you'll realize the problem was never your writing skills.

Registration link: https://api.thistoken.ai/register

---

Tired of juggling provider integrations? Register at https://api.thistoken.ai/register and call every model through one base_url.