Weekly Report Generator

Problem

Weekly reports often become task lists: work is listed, but value is unclear; impact is claimed, but evidence is missing; notes are scattered and need reformatting before pasting into Feishu or Notion. This skill focuses on organizing supplied material and rewriting it for a professional update, not on inventing work. It is useful for turning personal notes into a version that can be sent to a tech lead or business lead.

How it works

It accepts daily notes, task lists, or rough work fragments. First it confirms role, audience, and priorities, then groups items by project, development, testing, meetings, or other types.
- Rewrites “did an interface” into “completed interface integration and reduced rework”
- Prompts for quantified evidence such as throughput, duration, or improvement rate
- Produces a detailed, concise, or executive version, with optional next-week plans

Boundaries

It does not connect to code repositories, time-tracking systems, or business databases. If the input is too thin, it can only draft from limited information and ask for more. It is not intended for daily reports, monthly reports, year-end reviews, or OKR planning. Users should avoid asking it to fabricate unperformed work and should sanitize client names or internal codenames first.