AI Weekly Report Assistant

Problem Solved

Weekly reporting often fails because notes are scattered and the final draft reads like a diary. This skill turns a short description of the week into a submittable weekly report, organized around deliverables, blockers, and next steps.

How It Works

Input can be a few lines, for example: Did requirement review, implemented 3 APIs, fixed 2 bugs, attended 2 meetings, and launch is planned next week. The skill generates a structured report:
- Completed this week: focuses on concrete outcomes and keeps useful metrics.
- In progress: states current status and blockers.
- Next week's plan: lists checkable follow-up actions.
- Risks / Support needed: makes coordination needs explicit.

If the user only says help me write a weekly report, it returns a general template and asks for the week's work items. It can also switch tone, such as formal reporting, brief sync, or data-driven styles.

Scope and Notes

It is useful for quickly drafting a weekly report, but it does not pull data from Git, Jira, or meeting notes by itself. Output quality depends on factual detail in the input: task names, numbers, risks, and dependencies make the report more useful. It avoids diary-like phrasing and downplays weak claims such as learning a technology unless that is the main outcome.