md-report-summary

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Markdown 周报 / 汇报 / 总结 / 介绍

Markdown Weekly Report / Work Report / Summary / Introduction

一、任务识别

I. Task Identification

文档类型触发词
周报周报、本周总结、weekly report
工作汇报工作汇报、汇报材料、进度汇报
总结总结、复盘、阶段总结、项目总结
介绍介绍、简介、项目介绍、个人介绍
Document TypeTrigger Words
Weekly Reportweekly report, this week's summary, weekly report
Work Reportwork report, report materials, progress report
Summarysummary, review, phase summary, project summary
Introductionintroduction, profile, project introduction, personal introduction

二、流程分支

II. Process Branches

情况执行
未提供草稿执行「三、无草稿流程」
已提供草稿执行「四、有草稿流程」
ScenarioAction
No Draft ProvidedExecute "III. Process for No Draft"
Draft ProvidedExecute "IV. Process for Existing Draft"

三、无草稿流程

III. Process for No Draft

  1. 确认信息:向用户确认主题、时间范围、受众、重点方向
  2. Web 搜索:用
    WebSearch
    搜索相关背景、行业进展、最佳实践(搜索结果仅作参考,不可直接照抄)
  3. 选模板:按 reference/templates.md 选择对应模板
  4. 撰写:按「六、写作质量标准」填充内容并输出
  1. Confirm Information: Confirm the topic, time range, audience, and key directions with the user
  2. Web Search: Use
    WebSearch
    to search for relevant background, industry developments, and best practices (search results are for reference only, do not copy directly)
  3. Select Template: Choose the corresponding template according to reference/templates.md
  4. Write: Fill in the content and output according to "VI. Writing Quality Standards"

四、有草稿流程

IV. Process for Existing Draft

  1. 读取草稿:读取用户粘贴的内容或文件路径中的草稿
  2. 分析草稿:识别结构完整性、遗漏点、可优化表述
  3. 整理输出
  • 表格、列表、引用块、数据、图片全部原样保留,不删减、不概括
  • 图片引用
    ![描述](路径)
    路径不可修改,原样保留
  • 润色语句、理顺段落逻辑、补充过渡语
  • 缺失章节可用
    WebSearch
    补充,但需注明为补充内容
  1. 输出:整理后的完整 Markdown
  1. Read Draft: Read the draft pasted by the user or from the file path
  2. Analyze Draft: Identify structural completeness, missing points, and optimizable expressions
  3. Organize and Output:
  • Keep tables, lists, blockquotes, data, and images exactly as they are; do not delete or summarize
  • Do not modify the path in image references
    ![description](path)
    , keep it as is
  • Polish sentences, clarify paragraph logic, and add transitional phrases
  • Missing sections can be supplemented using
    WebSearch
    , but must be marked as supplementary content
  1. Output: The complete organized Markdown

五、通用原则

V. General Principles

  • 不省略:有草稿时,原内容(表格、数据、图片、引用块)全部保留
  • 不编造:不虚构草稿中不存在的事实;搜索补充内容需概括性表述,不夸大
  • 图片原样
    ![描述](路径)
    中的路径绝对不能修改
  • 格式统一:标题层级清晰,列表、表格按需使用,不滥用加粗
  • Do Not Omit: When a draft is provided, retain all original content (tables, data, images, blockquotes)
  • Do Not Fabricate: Do not invent facts that do not exist in the draft; supplementary content from searches should be generalized and not exaggerated
  • Keep Images As Is: The path in
    ![description](path)
    must not be modified
  • Unified Format: Clear title hierarchy, use lists and tables as needed, do not overuse bold formatting

六、写作质量标准

VI. Writing Quality Standards

高质量输出需满足以下要求:
High-quality output must meet the following requirements:

内容层面

Content Level

  • 有结论,不只有陈述:每个工作项应写清楚"做了什么 → 结果/进展如何",而非只罗列动作
    • 🚫 差:
      完成了模型测试
    • 👍 好:
      完成 Qwen3.5-122B-A10B-AWQ 在 4×24G NVIDIA 环境下的高考模拟卷测试,错题率降至 1/18,推荐作为 NVIDIA 多卡方案首选
  • 数据具体:尽可能保留时间、数量、百分比等量化信息
  • 问题定位清晰:问题描述需包含"现象 → 根因 → 影响范围"三要素
  • 计划可执行:下周计划要具体,写清楚目标和预计时间,不写"继续推进"类空话
  • Include conclusions, not just statements: For each work item, clearly write "what was done → what the result/progress is", rather than just listing actions
    • 🚫 Poor:
      Completed model testing
    • 👍 Good:
      Completed the college entrance examination simulation paper test of Qwen3.5-122B-A10B-AWQ in a 4×24G NVIDIA environment, with the error rate reduced to 1/18. Recommended as the preferred multi-card solution for NVIDIA
  • Specific Data: Retain quantitative information such as time, quantity, and percentage as much as possible
  • Clear Problem Localization: Problem descriptions must include the three elements: "phenomenon → root cause → scope of impact"
  • Executable Plans: Next week's plan must be specific, clearly stating the goals and expected time; avoid vague phrases like "continue to promote"

结构层面

Structure Level

  • 小标题区分不同业务模块,避免将所有内容塞进一个列表
  • 多项工作优先用表格呈现对比(如模型测试结果),清晰直观
  • 重要结论或推荐可用**引用块(
    >
    )**突出
  • Use subheadings to distinguish different business modules; avoid putting all content into a single list
  • Prioritize using tables to present comparisons for multiple work items (such as model test results) for clarity and intuitiveness
  • Highlight important conclusions or recommendations using blockquotes (
    >
    )

语言层面

Language Level

  • 主动语态,简洁直接
  • 专业术语保留(如模型名称、参数名、配置规格),不转译成模糊表述
  • 同一事物前后用词一致
  • Active voice, concise and direct
  • Retain professional terms (such as model names, parameter names, configuration specifications); do not translate them into vague expressions
  • Use consistent terminology for the same thing

七、参考资源

VII. Reference Resources

  • 模板文件:reference/templates.md
  • Template File: reference/templates.md