Overview
It reduces the burden of writing the weekly report that comes around every week from scratch each time, wondering "what did I even do." It organizes the week's work into a set framework of achievements, in-progress items, issues, and next week's plans, and polishes the sentences to match the recipient (team lead, executive, colleague) and the organization's tone to create a submission-ready draft. This skill absorbs and replaces the existing moai-coworker:collab-pm-report.
Trigger Keywords
weekly report, weekly work report, work report, week review, what I did this week, work log, weekly work summary, weekly report, weekly report
Workflow
Step 1: Collect the week's work
First, gather the scattered work of the week (from work logs, messengers, commits, calendars).
- Completed work: tasks and deliverables finished
- In-progress work: tasks not yet finished and their current stage
- Issues/blockers: points that are stuck, areas where help is needed
- → If you keep a work log regularly, this step takes just 1 minute →
doc-notion-templateintegration
Step 2: Organize around achievements
Organize so that "results and impact" are visible, not just "a list of things done."
- In the form of task (what) → result (how it turned out, numbers)
- "Wrote a report" → "Completed the new campaign report, scheduled for executive briefing next week"
- If possible, include figures (counts, rates, amounts, deadlines) to make it objective
- → Let the recipient immediately know "so what happened, and how"
Step 3: Place into the standard report framework
Fill in the 4-block framework commonly used in organizations.
| Block | Content |
|---|---|
| Key achievements this week | 3–5 key items completed or making progress |
| In-progress tasks | Current stage and expected completion time |
| Issues/requests | Stuck points, requests for decisions or support |
| Next week's plans | 3 things to focus on next week |
→ Don't write too long. Just the essentials, readable in under 1 minute.
Step 4: Match tone and formality
Decide the sentence tone to match the recipient and organizational culture.
- Formal style (executives, official reports): "~하였습니다", concise bullet-style + tidy endings
- Casual style (close team, Slack): "~했어요/했습니다", soft and quick
- Bullet-style vs prose-style: bullet-style for quick scanning, prose-style when context explanation is needed
- → The same content can be presented in two versions just by changing the tone
Step 5: Final check
- Attach requests to issues: For blockers, specify up to "what you need help with"
- Next week's plan priorities: Narrow down to 3 and
productivity-timeplace blocks with - Polishing AI-ness: Remove awkward translationese and excessive embellishment →
moai-coworker:ai-slop-reviewerpost-processing recommended - → If you need a weekly retrospective,
productivity-retrolightly continue to
Usage examples
Example 1: "Summarize what I did this week and write a weekly report to send to my team lead" → Collect tasks → Organize into 4 performance-focused blocks → Formal, bullet-style draft
Example 2: "Lightly organize a weekly update to post on Slack" → 3–5 key points → Conversational tone → Short scannable format
Example 3: "I have something blocked this week—how should I write it in the report?" → Issue + specify "needed decision/support" → Reflect follow-up in next week's plan
Deliverables
- Weekly task collection and organization
- Performance-focused 4-block report (achievements, progress, issues, next week's plan)
- Tone-specific versions (formal/conversational)
- Requests attached to issues and 3 next-week priorities
Precautions
- Focus on "results/impact," not "listing what was done" — write from the recipient's perspective.
- The longer it is, the less it gets read. Keep only the essentials, readable within 1 minute.
- Report tone and format vary by organization. Match the recipient and existing format.
- Since this is a text deliverable, before submission
ai-slop-reviewerit is recommended to polish AI patterns with
Related skills
- moai-coworker:productivity-retro: Run weekly reports and weekly retrospectives together
- moai-officer:doc-notion-template: Automate report writing with a work log DB
- moai-officer:productivity-time: Place next week's plan into time blocks
- moai-coworker: Interpersonal communication such as report conversations, verbal reports, and feedback
- moai-coworker:ai-slop-reviewer: Post-process AI-ness in report drafts
- moai-writer:korean-humanize: Remove Korean AI-ness (required after slop review)
When not to use this skill
- Team-wide sprint reports and project progress reports: For organization-level reports, use
moai-coworker. - Verbal reports and meeting speech scripts: For verbal reports and feedback, send with
moai-coworker. - Official documents (approval requests, proposals, pitch decks): For formal document formats, the
moai-coworkerfamily is appropriate.
Source
Referenced general workplace weekly report writing frameworks (performance-focused 4 blocks, tone matching) and user vault work log notes. Expressions and examples are independently composed based on 2026 Korea standards. Absorbs and replaces the existing moai-coworker:collab-pm-report.