moai-pm | Korean weekly report culture + global best practices
Overview
Automatically creates a weekly report for the Monday morning WBR (Weekly Business Review) or Friday wrap-up report. It is based on the 6-section standard established in Korean workplace culture (KPI / Done / In Progress / Plan / Risks / Decisions), and simultaneously generates two versions: a 1-pager for executives and a detailed team-internal version.
Trigger Keywords
weekly report WBR weekly report weekly meeting materials weekly work report weekly report executive weekly report team weekly report
Real-world weekly report, meeting, and retrospective patterns (Korean team)
The weekly report is not a standalone deliverable but WBR meeting + retrospective + deciding next week's prioritiescomprehensive supporting material for. These are know-how optimized for Korean organizational culture.
6 Core Patterns
① Korean WBR standard 6 sections (already applied + vault verified)
| # | Section | Korean practical pitfalls |
|---|---|---|
| 1 | This week's highlights (KPI) | Must show % against target — reporting only absolute values ❌ |
| 2 | Done | "Worked hard" X, quantify impact (-30% cost, +15% users) |
| 3 | In Progress | Progress % + whether it is expected to be completed next week state clearly |
| 4 | Next week's plan (Plan) | P0/P1/P2 priority — do not estimate in time units |
| 5 | Issues and risks | Do not simply list X — impact + response plan accompany |
| 6 | Decision requests | Present 2-3 options — do not simply ask questions |
② Retrospective frameworks KPT and 4Ls (verified by Korean planners)
It is recommended to integrate a retrospective section into the weekly report. Choose one of two frameworks:
KPT (most common):
- Keep: what to continue
- Problem: what needs improvement
- Try: what to try anew
4Ls (including emotions):
- Likes: what was good and achievements
- Learned: what was learned (from success and failure)
- Lacked: what was lacking
- Longed for: what was hoped for
A retrospective expresses abstract thoughts in the head as 'readable language' → training the planner's essential competency, "communication ability."
③ Standard format for decision requests (reporting to Korean executives)
## 의사결정 요청 — [주제]
### 배경
[1~2줄 맥락]
### 옵션
| 옵션 | 장점 | 단점 | 비용·일정 |
|---|---|---|---|
| A (권장) | ... | ... | ... |
| B | ... | ... | ... |
| C | ... | ... | ... |
### 권장 사유
[1~2줄 핵심]
### 결정 마감일
[명시]
Questions like "I'm worried, what should we do?" X — executives want to see options + recommendations together.
④ Scrum Cadence Decision Matrix (Weekly Report Input)
| Project Phase | Recommended Scrum Cadence | Weekly Report Input |
|---|---|---|
| Fast Execution·MVP | Daily Scrum | Daily notes → weekly summary |
| General Development·Planning | 주 2-3회 | Directly integrate scrum notes |
| Review·Approval-focused | 주 1회 | Once a week + asynchronous updates |
| Long-term R&D | Biweekly | Biweekly + milestone report |
Scrum = raw input for the weekly report. If you organize your daily scrum notes in advance, the weekly report can be written within 30 minutes.
⑤ Automatic Tone Mapping (Reflecting Korean Organizational Hierarchy)
| Report Audience | 톤 | Tone Example |
|---|---|---|
| C-Level (CEO/CFO/COO) | Formal tone + conclusion first | "-합니다", "-로 판단됩니다" |
| Department Head·Team Leader | Formal tone | "-합니다", polite report style |
| Within the team (Slack) | Polite informal tone | "-했어요", "-할 예정이에요" |
| External Client | Formal tone + honorifics | "-하셨습니다", "-해 주시면 감사하겠습니다" |
| Retrospective (within the team) | Self-reflective style | "-했더라고요", "-를 배웠어요" |
For mixed reporting, output both versions simultaneously — 1-pager (executives) + full version (team).
⑥ Integration of 3 Meeting Facilitation Methods (Utilization of Weekly Report Deliverables)
| Meeting | Weekly Report Utilization |
|---|---|
| Planning Review | In-progress section + decision request items — branch into big picture vs execution plan |
| Scrum | KPI·progress section — quickly share current issues·blockers |
| Retrospective | KPT·4Ls section — this week's retrospective + next week's Try |
Planning review core 4 steps:
- Distinguish concept proposal vs execution plan — decide in advance who reviews what
- Attach documents in advance + specify the parts you want feedback on
- Avoid immediate rebuttal — prevent emotional conflict with phrases like "I will consider it sufficiently and review further"
- Share meeting minutes the same day — prevent listeners' memories from fading
Korean Weekly Report Anti-patterns
- Listing chronologically like a week's diary of actions (no impact)
- Only absolute values without KPI targets ("MAU 12,000" — unknown against target)
- Listing "10 things to do next week" without priorities
- Making decision requests as simple questions ("How should we do it?")
- Leaving the issues·risks section empty (signaling false peace)
- Data only without retrospective·insights
Tips for automatic data synchronization when entering into Notion·Linear·Asana
- Notion: Split the database view into
Done this week/In progress/Planned3 filters - Linear: Auto-group issues by Cycle → direct fetch when MCP is available
- Asana: Sort by Section + calculate progress with Status field
When no tools are available, fall back to free-text notes + LLM cleanup.
💡 Cumulative 1-year effect of Korean weekly reports: (1) Visualize your own work (2) Improve executive decision-making speed (3) Improve communication skills through habitual retrospectives. With one year of well-written weekly reports, both speaking and document-writing skills change.
Workflow
Step 1: Automatic data source detection (3-tier fallback)
| Tier | Source | Action |
|---|---|---|
| 1 | Notion·Linear·Asana MCP available | Automatically fetch database/issues |
| 2 | CSV/JSON upload | Parse external tool export |
| 3 | Free-text notes | Use the user's organized content as-is |
When MCP is available, automatically use it first. If the user explicitly enters text, process it as-is.
Step 2: Generate 6-section body (Korean WBR standard)
| # | Section | Content |
|---|---|---|
| 1 | This week's highlights (KPI) | Achievement of predefined metrics·% vs. target |
| 2 | Done | PR·ticket·feature units, quantify impact |
| 3 | In Progress | Items scheduled for completion next week·progress rate |
| 4 | Next week's plan (Plan) | priority labels (P0/P1/P2) — do not estimate in time units |
| 5 | Issues·risks | External dependencies, schedule pressure, technical debt |
| 6 | Decision requests | Items requiring executive/PM decisions + options |
Step 3: Automatically apply tone
If the user does not specify a tone, automatically map by audience:
- Executive report: Formal style ("-합니다", "-로 판단됩니다")
- Internal team (Slack, etc.): Polite style ("-했어요", "-할 예정이에요")
- Mixed: Output both versions simultaneously
Step 4: Generate a separate executive 1-pager (optional)
Compress to ≤ 250 words:
- 1-line KPI headline
- 3 key completed items (1 line each, quantified)
- 1 risk
- 1-2 decision requests
Step 5: Post-processing guide
- moai-coworker:ai-slop-reviewer: Review AI patterns·formal tone (required for text outputs)
- moai-writer:korean-humanize: Adjust for natural Korean (next step after ai-slop-reviewer)
- moai-coworker:collab-exec-summary: Convert the 1-pager into a more compressed C-level report
- moai-officer:doc-pptx: Output as slide presentation material
Output format
# 주간보고 — [팀명] (2026년 W18, 5/1~5/7)
## 1. 이번 주 핵심 (KPI)
- MAU: 12,450 (목표 12,000 대비 +3.8%)
- 신규 가입: 320 (목표 300 대비 +6.7%)
## 2. 완료 (Done)
- [Feature] 결제 페이지 v2 — PR #234 머지, 결제 성공률 +2.1pp
- [Bug] 로그인 500 에러 — 영향 사용자 ~30명, 핫픽스 배포
## 3. 진행 중 (In Progress)
- 알림 시스템 리팩토링 — 70% 완료, 차주 머지 목표
## 4. 차주 계획 (Plan)
- [P0] 결제 모듈 보안 감사 대응
- [P1] 마케팅 캠페인 페이지 제작
- [P2] 백엔드 의존성 업데이트
## 5. 이슈·리스크
- 외부 SMS API 응답 지연 → backup 채널 검토 필요
- 디자인팀 리소스 부족으로 차주 일부 작업 후순위
## 6. 의사결정 요청
- 보안 감사 대응 인력 추가 (옵션 A: 외주, B: 내부 재배치)
Executive 1-pager (≤ 250 words):
# Executive Brief — W18
**KPI**: MAU 12.4K (+3.8% vs 목표), 가입 320 (+6.7%)
**완료**: 결제 v2 머지(전환 +2.1pp) / 로그인 500 핫픽스 / 알림 70%
**리스크**: SMS API 지연 — 백업 채널 검토 중
**결정 요청**: 보안 감사 대응 — 외주 vs 내부 재배치
Usage examples
Example 1 — Notion MCP automatic fetch
사용자: "이번 주 주간보고 만들어줘. 우리 팀 Notion DB 'Weekly Tasks' 참고."
→ Notion MCP로 W18 완료 태스크·진행 중 자동 수집
→ 6섹션 격식체 보고 + 임원 1pager 두 버전 출력
Example 2 — Free-text fallback (polite style)
사용자: "이번 주 한 일 정리해줘. 결제 v2 머지했고, 로그인 버그 잡았고, 알림 리팩토링 70% 됐어."
→ 자유 텍스트 파싱 후 해요체 팀 내부 보고로 변환
Precautions
- Do not estimate time: Convert direct date·time estimates such as "complete by next Tuesday" into priority labels
- Do not evaluate individuals: Team member personal criticism/praise is not automatically included in the body (separate 1:1 if needed)
- No unverified figures: Specify KPI data source (BI tool/internal DB) or tag as [estimated]
- Caution with NDA information: Automatic check for company confidential information when writing reports for external sharing (
moai-lawyer:legal-nda-triagerecommended)
Built-in modes — Standup summary / Retrospective
This skill handles two auxiliary modes together without invoking a separate skill.
Standup summary mode (organizing input for the weekly report)
- Accumulate and compress daily standup notes (done/in progress/blockers) on a weekly basis
- Enter this mode for requests like "organize this week's standups" or "gather my daily notes"
- Connect the organized results directly as raw input (done/in progress/issues) for the 6-section weekly report
Retrospective mode (KPT·4Ls)
- Use the "② Retrospective framework KPT·4Ls" table above to generate the quarterly/sprint retrospective section
- Enter this mode for requests like "this quarter's retrospective" or "organize the sprint retrospective"
- Integrate into the weekly report body as a retrospective section, or output as a standalone retrospective document
Related skills
Before:
- (Notion·Linear·Asana MCP) — automatic data fetch (standup notes are organized directly via the "Standup summary mode" above)
After (text output post-processing — standard chain):
moai-coworker:ai-slop-reviewer— AI pattern reviewmoai-writer:korean-humanize— Korean naturalness correction (after ai-slop-reviewer)moai-coworker:collab-exec-summary— Compress further into a C-level 1-pagermoai-officer:doc-pptx— Presentation slide output
Alternative:
moai-officer:productivity-briefing— Daily report (daily, not weekly)
Related commands
- Registered skill chains:
- Weekly report body post-processing (standard):
weekly-report → moai-coworker:ai-slop-reviewer → moai-writer:korean-humanize → 최종 검수 - Weekly report → executive 1-pager:
weekly-report → moai-coworker:ai-slop-reviewer → moai-writer:korean-humanize → moai-coworker:collab-exec-summary - Presentation slides:
weekly-report → moai-coworker:ai-slop-reviewer → moai-writer:korean-humanize → moai-officer:doc-pptx
- Weekly report body post-processing (standard):
Sources
- Global best practices: Notion AI WBR template (4 sections: KPI/Done/Plan/Risk), Linear Cycles in 1-2 week units, Asana Status Updates (Green/Yellow/Red)
- Korean workplace culture: Monday morning WBR, Friday wrap-up report
- McKinsey Pyramid Principle (conclusion → evidence → data)