Organize the user's description of this week's work into a clearly structured Chinese weekly report with a friendly tone, and save it as a Markdown file.
Weekly Report Structure
The weekly report consists of two parts:
1. Opening Summary
Use 1-2 sentences to summarize the focus of this week's work, with a tone as natural as chatting with a colleague. Do not use formal forms of address like "尊敬的领导" (respected leader), and do not be too casual either. The goal is to let the reader know at a glance what the main work was this week.
Good examples:
- "This week was mainly spent advancing the refactoring of the user system, while also handling a few production issues."
- "This week's focus was on the Q2 requirements review and technical solution design, and I also fixed two backlogged bugs."
Styles to avoid:
- Too formal: "The work report for this week is as follows; please review it, leaders."
- Too casual: "Slacked off all week haha."
- Too empty: "Completed multiple work tasks this week."
2. Task Table
Present it in a Markdown table with three columns:
| Task | Progress | Notes |
|---|---|---|
| Specific task description | Progress status | Supplementary explanation |
Task column: Briefly describe what was done; it does not need to be too detailed but should be understandable. If the user's description is too general, appropriately add details to make it more informative.
Progress column: Use text descriptions; commonly used ones include:
- Completed
- In progress (a percentage can be added as a supplement, such as "In progress, about 70%")
- Not started
- Launched
- Submitted for testing
- Reviewed
Choose the most appropriate status based on the actual situation described by the user; do not apply them mechanically.
Notes column: Put supplementary information here, such as:
- Problems encountered or blockers
- Plans for next week
- Matters requiring assistance
- Related people or teams
If there is nothing particular to explain, the Notes column can be left blank (filled with - ).
Information Organization Principles
The user may describe the work content very casually; what you need to do is:
- Categorize and merge: Merge related small items into one task to avoid making the table too fragmented. For example, "fixed the login page styles" and "adjusted the registration page spacing" can be merged into "Fixed style issues on the login/registration pages."
- Supplement and infer: If the user says "done", the progress is "Completed"; if they say "still working on it", it is "In progress"; if they say "just started looking at it", it is "In progress, about 10%".
- Order reasonably: Sort by importance or workload, placing important tasks first.
- Preserve the original meaning: Do not add work content the user did not mention; organizing ≠ fabricating.
File Saving
Save as weekly-reports/weekly-report-YYYY-MM-DD-<序号>.md, using the current date as the date. Save the file in the current working directory.
If a file with the same name already exists in the current directory, prompt the user whether to overwrite it.
Complete example
User input:
This week I finished the cache optimization for the product details page and shipped it. I'm still working on the order export feature, about halfway done. I also reviewed a few PRs for the frontend team and handled one production alert.
Generated weekly report:
# 周报 - 2026-04-24
这周主要完成了商品详情页的缓存优化并成功上线，订单导出功能也在稳步推进中。
| 任务 | 进度 | 备注 |
|------|------|------|
| 商品详情页缓存优化 | 已上线 | 优化完成并部署上线 |
| 订单导出功能开发 | 进行中，约 50% | 预计下周完成 |
| 协助前端团队 Code Review | 已完成 | 审核了多个 PR |
| 处理线上告警 | 已完成 | - |