Generate weekly reports, monthly reports, quarterly reports, and annual summaries.
Report Types
| Type | Time Range | Input Source | Main Content | Format Requirements |
|---|---|---|---|---|
| Weekly Report | This week | Daily work records/dictated bullet points | This week's work, next week's plan | Fixed format, see template |
| Monthly Report | 4-5 weeks of the current month | Weekly report summary | Summary of main work, progress tracking | Flexible, highlight key work and progress |
| Quarterly Report | 12-13 weeks of the current quarter | Weekly report summary | Quarterly work summary, phased achievements | Flexible, highlight key work and progress |
| Annual Summary | 52 weeks of the year | Weekly report summary | Performance achievement, personal growth, growth plan | Fixed format, see template |
Usage Process
Step 1: Determine the report type and time range
First confirm the report type the user needs to generate:
- Weekly Report: Specify the week (e.g., this week, 2025.01.06 - 2025.01.10)
- Monthly Report: Specify the month (e.g., December 2025)
- Quarterly Report: Specify the quarter (e.g., Q4 2025)
- Annual Summary: Specify the year (e.g., 2025)
Step 2: Collect necessary information
Before starting, confirm the following information with the user:
- Weekly report file path: Files containing weekly reports (supports .rtf, .docx, .md, .txt formats)
- Planning document path(optional, recommended for annual summaries): Annual work planning document
- Supplementary information(optional): Listing of items and planning completion progress
- Reference format(optional): Report format template or reference images
- Role information(required for annual summaries):
- Current position
- Whether there were role changes during the period (e.g., from project manager to architect)
- Timing of role changes
- User guidance(important):
- Key work scope: Which work the user wants to highlight
- Content that needs to be downplayed or ignored
- Possible deviations in the weekly report or areas that need correction
- Other special requirements
Step 3: Read and parse files
Use the following method to read rtf files:
textutil -stdout -convert txt "文件路径.rtf"
For .md or .txt files, use the Read tool directly.
Step 4: Analyze weekly report content
- Organize by timeline: Organize weekly reports in chronological order, and filter weekly reports within the specified time range
- Segment by role: If there are role changes, distinguish the work content of different stages
- Extract key work：
- Key projects and versions
- Technical solutions and architecture work
- Team management work (if applicable)
- Cross-team collaboration
- Issue handling and optimization
- Identify results：
- Completed projects/versions
- Technical issues resolved
- Optimization effects and data
- Documents and solutions produced
Step 5: Generate content according to the report type
Weekly report generation
Weekly reports support two input modes:
Mode 1: Based on daily work records
The user provides daily work record files or notes, and Claude summarizes and organizes them into a weekly report:
- Read daily work records
- Classify work content by project/module
- Extract key progress and results
- Identify problems encountered
- Infer next week's plan based on context
Mode 2: Based on dictation/bullet points
The user directly dictates or briefly lists this week's work, and Claude organizes it in the standard format:
- Collect the work points provided by the user
- Ask for supplementary information (goals, progress, summary, thoughts, etc.)
- Organize and output in the standard weekly report format
Weekly report output format
Generate according to the fixed template format, see templates/weekly-report.md
Monthly report generation
The monthly report focuses on highlighting the main work and progress of the month, with a flexible format, and it is recommended to include:
- Key work of this month: Summarize the main work of the month by project/module
- Work progress: Completion status and progress percentage of each work item
- Main results: Results delivered and problems solved during the month
- Problems encountered: Blockers and risk points
- Next month's plan: Key work arrangements for next month
Quarterly report generation
The quarterly report focuses on highlighting the quarterly work summary and phased results, with a flexible format, and it is recommended to include:
- Quarterly work overview: Main work directions and goals of this quarter
- Key project progress: Summarize the work and progress within the quarter by project
- Phased results: Milestones and deliverables completed this quarter
- Problems and improvements: Main problems encountered and solutions
- Next quarter's plan: Key work planning for next quarter
Year-end summary generation
Generate according to the fixed template format, including the following sections:
- Performance achievement (1500-3000 words)
- Personal growth (400-700 words)
- Growth plan (400-700 words)
For detailed templates, see templates/year-end.md
Step 6: Combine with planning documents (applicable to year-end summaries)
If a planning document is provided:
- Extract the key work priorities for the next year
- Identify resource requirements
- Sort out personal growth directions
Step 7: Output the file
Output the generated report as a Markdown file, saved by default to the same directory as the weekly report.
Important Notes
- Respect User Guidance: The key work scope and correction instructions provided by the user have the highest priority
- Present Objectively: Avoid exaggerating achievements; speak with facts and data
- Highlight Value: Emphasize the actual impact of the work on the business and the team
- Clear Structure: Use tables and lists to improve readability
- Handling Weekly Report Discrepancies：
- The weekly report may have omissions or inaccurate descriptions
- Make corrections and additions according to user guidance
- If there are questions, proactively ask the user to confirm
Interaction Examples
Weekly Report Example (Based on Daily Records)
用户：帮我生成本周的周报
Claude：好的，我需要了解一些信息来生成周报：
1. 请提供本周的每日工作记录文件路径，或者直接告诉我你这周做了哪些工作
2. 本周的时间范围是？（如 2025.01.06 - 2025.01.10）
3. 汇报对象是谁？（用于称呼）
Weekly Report Example (Based on Spoken Bullet Points)
用户：帮我写周报，这周主要做了：
- AISE 项目文档规范
- Apifox 部署上线
- 代码追踪 MCP 协议开发
Claude：好的，我来帮你整理成周报。请补充以下信息：
1. 本周的工作目标是什么？
2. 各项工作的进度如何？（如：已完成、进行中 80%）
3. 有没有需要总结的成果、问题或未完成事项？
4. 有什么感想或改进建议？
5. （可选）有没有发现无效工作或浪费现象？
6. （可选）岗位提升方面有什么进展？
Monthly Report Example
用户：帮我生成 12 月的月报
Claude：好的，我需要了解一些信息来生成月报：
1. 请提供包含 12 月周报的文件路径
2. 你希望重点突出哪些工作？
3. 有哪些内容需要弱化或忽略？
Quarterly Report Example
用户：帮我生成 Q4 季报
Claude：好的，我需要了解一些信息来生成季报：
1. 请提供包含 Q4（10-12 月）周报的文件路径
2. 本季度有哪些重点项目需要突出？
3. 有哪些内容需要弱化或忽略？
Year-End Summary Example
用户：帮我生成年终总结
Claude：好的，我需要了解一些信息来生成年终总结：
1. 请提供周报文件的路径
2. 是否有下一年度的规划文档？
3. 请告诉我你的岗位信息，以及年内是否有角色变化
4. 有没有参考的格式模板？
5. 请提供一些指引：
- 你希望重点突出哪些工作？
- 有哪些内容需要弱化或忽略？
- 周报中有没有需要修正的地方？
Handling Common Questions
Q: What should I do if the weekly report has too much content and the summary is too long?
A: Filter according to the key scope specified by the user; secondary work can be merged or described more concisely.
Q: What should I do if the weekly report format is inconsistent?
A: Try to identify the key information (time, work content, results); format differences do not affect content extraction.
Q: What should I do if the user does not provide a planning document?
A: The growth plan section can be written based on the growth directions and areas for improvement reflected in the weekly report, or you can ask the user to provide additional information.
Weekly Report Format Suggestions
To better support the generation of various reports, users are advised to write weekly reports in a standard format.