---
name: team-weekly-report-generation
description: Use when teammates need to turn scattered Chinese work notes into a unified weekly report for 康比特数字技术中心 / 数科业务, especially when the user says 写周报, 整理周报, 统一周报, 本周工作, 下周计划, or asks to generate reports from team work records.
---

# Team Weekly Report Generation

## Purpose

Generate consistent, executive-facing Chinese weekly reports for the 康比特数字技术中心 / 数科业务 context.

Default user-facing weekly report output is now the事业部周报 Excel template, not Markdown or HTML:

```text
/Users/jack/同步空间/cpt/05_经营管理与会议/005_日常管理/周例会（事业部层面）/2026年/周报模板.xlsx
```

Markdown remains acceptable only for internal source notes, evidence, and project memory. Do not present Markdown or HTML as the final weekly report deliverable unless the user explicitly asks for those formats.

User-facing weekly report workbooks must use `微软雅黑` at `12` pt as the default visible font. Apply this to all cells in the workbook, including preserved template sheets and any added sheets such as `图文看板`. Keep bold/color/fill where useful, but normalize font family and size before delivery.

This project skill extends the general `weekly-report` skill with the project-specific knowledge base:

```text
standards-stack/weekly-report/weekly_report_memory_knowledge_base_markdown_cn.md
```

## Trigger

Use this skill when:

- the user asks to 写周报、整理周报、统一周报、生成本周工作总结 or 输出下周计划
- teammates provide scattered work notes and need a unified Markdown report
- the report should reflect product standardization, project delivery, AI enablement, risk control, SOP沉淀, or executive reporting language
- the user asks to reuse the project weekly report knowledge base in Codex Agent or other models

## Required Context

Read, in order:

1. `/Users/jack/.codex/skills/weekly-report/SKILL.md` for the general report workflow.
2. `standards-stack/weekly-report/README.md`.
3. `standards-stack/weekly-report/weekly_report_memory_knowledge_base_markdown_cn.md`.
4. If the report is for leadership, cross-team coordination, strategy review, or should avoid流水账, also read `standards-stack/agent-skills/skills/weekly-report-strategic-transparency/SKILL.md`.
5. If the report involves 数科业务 / 数字化体育科技 / 智慧营养健康餐厅, also read `standards-stack/agent-skills/skills/digital-business-investor-strategy-lens/SKILL.md`.
6. For the final deliverable, load the template workbook at `/Users/jack/同步空间/cpt/05_经营管理与会议/005_日常管理/周例会（事业部层面）/2026年/周报模板.xlsx`.

If the report is tied to a specific project, also read the matching project workspace entry, for example `work_store/`, `work_ai_api/`, `product_pingan_yunchu/`, or `work_sch1.0new/`.

## Workflow

1. Intake the raw material.
   - Accept bullets, chat records, task lists, Yunxiao items, PR/MR notes, screenshots, or rough prose.
   - Extract facts first: project, action, result, status, risk, next step, owner, date.

2. Classify by natural business boundary.
   - Prefer: product standardization, project delivery, AI application, management/SOP, presales/customer support, risk and next week.
   - Keep user-provided project names and customer names when available.

3. Apply project expression rules.
   - Apply the pyramid principle by default: first write the conclusion, then the supporting points, then the evidence. For each major section, use `结论 -> 分论点 -> 证据/数据/产物路径 -> 下一步` instead of listing raw activity.
   - Use `standards-stack/management/product-development-department/PRODUCT_RND_STRATEGY_2026.md` as the default product/R&D strategy reporting contract.
   - Keep the first-level strategy tags fixed as `产品差异性`, `产品标准化`, and `AI赋能`; second-level tags may be expanded as evidence accumulates.
   - Weekly inputs should preserve the daily-report fields: core conclusion, strategy tag, second-level tag, evidence, metric signal, reusable asset, risk/dependency, and next step.
   - Emphasize business progress, productization, standardization, AI efficiency, delivery closure, and reusable capability.
   - Avoid流水账、空话、夸大、无结论描述.
   - For each important item, clarify: background -> action -> result/status -> value -> next step.
   - For leadership or strategic reports, add mainline task progress, decision reasoning, and intelligence/field-of-vision signals.
   - For 数科业务, connect each major item to revenue, margin, standard reuse, recurring service revenue, cash collection, main-business synergy, defensibility, or ROI; do not stop at project count or feature completion.

4. Apply the bottom-layer weekly report logic.
   - Do not write "I did many things"; write "I layered the work, managed it by SOP, landed it through product planning, used AI to turn one-off business into reusable assets, and used Before / After to explain value."
   - Classify first, then report: 产品层 -> 项目层 -> AI层 -> 沉淀层 -> 价值层.
   - Use `SOP + 产品规划表` as the backbone. Every meaningful project should show its SOP stage, this week's action, next week's deliverable, and reusable value; every meaningful product/module should show this week's artifact, next week's artifact, and month-end target when the source supports it.
   - Use `Before / After` as the expression method for AI, automation, product standardization, and management process changes.
   - Express AI as `来说话、干事、沉淀资产`: speech means meeting minutes, PRD, scripts, manuals, FAQs, weekly reports; action means requirements decomposition, Yunxiao task drafting, test-case generation, Playwright execution, reports, operation videos, and training materials.
   - Treat one-off business workflows as asset seeds. A flow such as `新增人员 -> 发卡 -> 挂失 -> 冻结 -> 退卡 -> 补卡` should be examined for SOP, test cases, automated test scripts, operation video, user manual, HTML report, and FAQ/sales-after knowledge.

5. Handle missing information.
   - Do not fabricate numbers, completion status, customer feedback, or strategic outcomes.
   - If information is missing but the report can still be drafted, write the current state and next step.
   - Ask only short follow-up questions when the missing information changes the conclusion.

6. Output the weekly report.
   - Default to the Excel workbook template, preserving the `项目` and `产品` sheets.
   - Normalize the workbook font to `微软雅黑` 12 pt before delivery.
   - Use the `项目` sheet for project list/status, following the template columns: 项目类型、项目阶段、项目名称、关键时间、项目金额、负责人、合同、采购、交付、上线、验收、回款、上周进展、本周计划/后续动作、问题与偏差、备注、链接。
   - Use the `产品` sheet for product work, following the template columns: 一级分类、二级分类、工作内容、对应项目/场景、时间节点、负责人、本周输出/目标、备注。
   - Add a visual dashboard sheet when useful, such as `图文看板`, with charts, image cards, or compact visual summaries for project stage distribution, product mainlines, 证书状态, risks, and next-week priorities.
   - Each main item should follow pyramid order:
     - conclusion: what changed or what judgment was reached
     - supporting points: product/project/AI/SOP/value dimensions
     - evidence: source record, artifact path, metric, screenshot, task id, or clearly marked gap
     - next action: owner or next deliverable when known
   - Place generated weekly report workbooks under `work/weekly-reports/<week>/<topic>/`, and copy a convenience copy to `/Users/jack/Downloads/` when the user needs to review or share it.

## Quality Bar

- The report should sound formal, concise, and suitable for executives.
- Every major item should answer "why it matters", not only "what was done".
- Every major section should be readable from the first sentence alone; details should only support or qualify that conclusion.
- Risks must include impact and mitigation action.
- AI should be expressed through workflow change, efficiency gain, delivery improvement, or capability building.
- Product work should connect to standard product, configuration, module reuse, SOP, or scene replication.
- The final report should show hierarchy: product planning, project SOP stage, AI enablement, reusable asset, and value/Before-After.
- Avoid vague status words such as `跟进中`, `推进中`, or `沟通中` unless followed by stage, artifact, blocker, and next deliverable.

## Validation

Before finalizing:

- Check that all facts are traceable to user-provided material or known project context.
- Check that no uncertain item is written as completed.
- Check that every risk has a response or next action.
- Check that the Excel workbook opens with `openpyxl`, preserves the required `项目` and `产品` sheets, and includes visual material when the user asks for 图文并茂.
- Check that visible workbook cell fonts are normalized to `微软雅黑` 12 pt.
- Check that the report can be read as "from doing tasks to building a system": SOP-managed, product-planned, AI-enabled, asset-reusable, and Before/After-explainable.