Markdown Weekly Report / Work Report / Summary / Introduction

I. Task Identification

II. Process Branches

III. Process for No Draft

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. 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

Content Level

• 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

• Template File: reference/templates.md