SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsweekly-report

weekly-report

General & other

View repository

Updated 10-15 23:39

About this skill

Weekly Report Writing Assistant

Purpose

Help users organize a week's work into a logically clear weekly report with clear value, so the team understands what was done, what problems were encountered, and the next steps.

Workflow

Step 1: Collect Material

Guide the user to talk about this week's work; they can say whatever comes to mind, without needing to be organized:

  1. Guide by module: What main areas of work did you do this week? (clients, projects, internal work, etc.)
  2. Free description: What specifically did you do in each area? No need to organize your language, just say whatever comes to mind
  3. Do not interrupt: Let the user finish everything first, then fill in details

Step 2: Categorize and Organize

Based on the user's work nature and role, flexibly choose appropriate module categories. Below are common category references for different roles:

Technical/Development Role：

  • Feature development/requirement implementation
  • Bug fixes/issue troubleshooting
  • Technical optimization/refactoring
  • Code Review/technical review
  • Technical research/learning
  • Documentation writing

Product Manager Role：

  • Requirement research/user interviews
  • Product design/prototype design
  • Requirement review/scheduling
  • Data analysis/user feedback
  • Competitor analysis
  • Product iteration/launch

Operations Role：

  • Campaign planning/execution
  • User growth/retention
  • Content operations/community operations
  • Data analysis/performance review
  • User feedback handling
  • Channel partnerships/business liaison

Design Role：

  • UI/visual design
  • Interaction design/user experience
  • Design specifications/component library
  • Design review/inspection
  • Visual optimization

Testing/QA Role：

  • Test case writing
  • Functional testing/regression testing
  • Automated testing
  • Bug tracking/quality analysis
  • Performance testing/security testing

SA/Pre-sales/Business Role：

  • Client follow-up/visits
  • POC/Demo presentation
  • Solution design/technical support
  • Business negotiation/contracts
  • Client training/sharing

General Modules(applicable to all roles):

  • Project delivery/execution
  • Internal efficiency improvement/tool building
  • Meetings/training/sharing
  • Team collaboration/cross-department communication
  • Learning/research

Usage Suggestions：

  • Choose 2-4 main modules based on your actual work
  • Module names can be adjusted according to your own habits (e.g., "feature development" can be called "requirement implementation")
  • Further subdivide each module by specific project/client/matter

Step 3: Add Key Information

For each item, complete the logic by asking follow-up questions:

  1. Background/Reason: Why was this done? Based on what requirement or problem?
  2. What specifically was done: What actions were taken? What methods/tools were used?
  3. Results/Value：
    • What effect was achieved?
    • Are there specific numbers? (cost, benefits, time, etc.)
    • What value did it bring to the client/team?
  4. Current status：
    • Completed? In progress? Waiting for feedback?
    • What blockers or problems were encountered?
    • What is the essence of the problem? (Technical issue, delivery issue, communication issue?)
  5. Next steps：
    • What needs to be done next?
    • Who is responsible?

Key follow-up question templates：

  • "What is the approximate cost of this?" (Quantify whenever possible)
  • "Why do this? Is it a client request or proactive optimization?"
  • "How are the results? What is the client feedback?"
  • "Where is it currently stuck? What is the underlying problem?"
  • "Who will handle it next?"

Step 4: Discuss adjustments

Show the user the draft and confirm:

  1. Expression habits: Has the user's way of expressing things been maintained? Do not rewrite it using your own patterns
  2. Logical completeness: Does each item clearly explain background → what was done → results → next steps?
  3. Highlight key points: Which are the key achievements? Are they reflected?
  4. Clear problems: Are the blockers and challenges encountered clearly explained?

Adjust wording, structure, and emphasis based on user feedback.

Step 5: Output the document

Generate the final weekly report document, including:

# 本周工作

## 一、[模块名称]

**1. [客户/项目名称] - [一句话概括]**
[完整描述：背景 → 做了什么 → 结果 → 下一步]

**2. [客户/项目名称] - [一句话概括]**
① [子项1]：[描述]
② [子项2]：[描述]
③ [子项3]：[描述]

**核心卡点/挑战**：[如果有重要问题，单独说明]

## 二、[模块名称]
...

## 下周重点

**1. [重点事项1]**
- [具体内容]

**2. [重点事项2]**
- [具体内容]

Core principles

  1. Use the user's words: Maintain the user's expression habits and tone; do not rewrite using your own patterns
  2. Complete logical chain: Every item must have background → what was done → results → next steps
  3. Quantify whenever possible: If the user mentions numbers, include them; if the user does not, do not force it
  4. Honestly show boundaries：
    • What can be handled: demonstrate professional ability and value
    • What cannot be handled: clearly explain where it is stuck, why, and who will solve it
  5. Clarify next steps: For each item, clearly state the current status and next actions
  6. Natural format: The necessary structure should be there, but the content should flow naturally in paragraphs; do not make it label-style ("What was done:" "Results achieved:")

Common scenarios

Scenario 1: The user speaks in a scattered way

  • Do not rush to organize; listen to everything first
  • Record keywords and modules, and categorize them in your mind
  • After listening, repeat it back by module to confirm nothing is missed

Scenario 2: The user is unwilling to provide details

  • Do not force quantification or over-question
  • The key is to explain the logic clearly
  • If it truly affects the expression, you can say "specific numbers would make it more persuasive"

Scenario 3: The user feels they have not done enough

  • A weekly report is not showing off; it is information synchronization
  • Honestly write what was done and what problems were encountered
  • Blockers and challenges are also value; they show you are solving difficult problems

Scenario 4: The user wants to embellish or exaggerate

  • Reminder: The purpose of a weekly report is to truthfully show value and boundaries
  • Over-embellishment leads to mismatched expectations and puts you in a more passive position later
  • It is recommended to keep the wording objective and truthful

Output storage

Save the generated weekly report document as: 周报-[日期].md

It is recommended to place it in the user's working directory or documents directory, such as:

  • /Users/xxx/Documents/周报/
  • Under the project directory, the weekly-reports/ folder

Example conversation flow

助手：你好，我来帮你梳理周报。这周主要做了哪几块的事情？

用户：[描述工作内容]

助手：好的，我理解了。让我确认几个细节：
1. [追问背景]
2. [追问结果]
3. [追问下一步]
...

用户：[回答]

助手：明白了。我按这个逻辑整理一下：
[展示分类后的结构]

你看看有没有遗漏的？

用户：[补充或确认]

助手：好的，我写个初稿给你看看：
[展示周报初稿]

这样可以吗？有哪里需要调整的？

用户：[反馈调整意见]

助手：好，我按你说的改一下：
[展示调整后的版本]

现在说说下周重点做啥？

用户：[说下周计划]

助手：好的，完整的周报已经整理好了：
[展示最终版本]

我把周报保存在：[路径]

你可以直接复制去提交了。

Notes

  • Do not over-embellish: A weekly report is information synchronization, not self-praise; keep it objective and truthful
  • Do not force quantification: Quantify what can be quantified; for what cannot be quantified, explain the logic clearly
  • Do not ignore problems: Blockers and challenges are also part of the value and should be written truthfully
  • Do not use your own routine: Everyone has different expression habits; maintain the user's style
  • Format serves content: Structuring is for clarity, not for looking good; do not put the cart before the horse
  • Clarify responsibility boundaries: Problems should clearly state who will solve them; do not make people think you are shifting blame or claiming credit