Work Report Generator
Generate weekly reports, monthly reports, quarterly reports, and year-end summaries.
Report Types
| Type | Time Range | Input Source | Main Content | Format Requirements |
|---|
| Weekly Report | This week | Daily work records/oral 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 key 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 |
| Year-end Summary | 52 weeks of the current year | Weekly report summary | Performance achievement, personal growth, growth plan | Fixed format, see template |
Usage Process
Step 1: Confirm Report Type and Time Range
First confirm the type of report 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)
- Year-end 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 year-end summaries): Annual work planning document
- Supplementary information (optional): Listing of items and progress of plan completion
- Reference format (optional): Report format template or reference image
- Role information (required for year-end summaries):
- Current position
- Whether there was a role change during the period (e.g., from project manager to architect)
- Time node of the role change
- User guidelines (important):
- Key work scope: Which work does the user want to highlight?
- Content to be downplayed or ignored
- Deviations in weekly reports that need correction
- Other special requirements
Step 3: Read and Parse Files
Use the following method to read
files:
bash
textutil -stdout -convert txt "文件路径.rtf"
For .md or .txt files, read directly using the Read tool.
Step 4: Analyze Weekly Report Content
- Organize by timeline: Sort weekly reports in chronological order and filter those within the specified time range
- Segment by role: If there was a role change, distinguish work content from different stages
- Extract key work:
- Key projects and versions
- Technical solutions and architecture work
- Team management work (if applicable)
- Cross-team collaboration
- Problem handling and optimization
- Identify achievements:
- Completed projects/versions
- Resolved technical issues
- Optimization effects and data
- Produced documents and solutions
Step 5: Generate Content Based on 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 them into a weekly report:
- Read daily work records
- Categorize work content by project/module
- Extract key progress and achievements
- Identify encountered problems
- Infer next week's plan based on context
Mode 2: Based on oral narration/bullet points
The user directly narrates or briefly lists this week's work, and Claude organizes it into a standard format:
- Collect work points provided by the user
- Ask for supplementary information (goals, progress, summary, reflections, etc.)
- Organize and output according to the standard weekly report format
Weekly Report Output Format
Generated according to the fixed template, see templates/weekly-report.md
Monthly Report Generation
Monthly reports focus on highlighting key work and progress of the month, with flexible format. It is recommended to include:
- Key work of the month: Summarize key work of the month by project/module
- Work progress: Completion status and progress percentage of various work items
- Main achievements: Deliverables and resolved issues of the month
- Encountered problems: Blockers, risk points
- Next month's plan: Key work arrangements for next month
Quarterly Report Generation
Quarterly reports focus on highlighting quarterly work summaries and phased achievements, with flexible format. It is recommended to include:
- Quarterly work overview: Main work directions and goals of the quarter
- Key project progress: Summarize work and progress within the quarter by project
- Phased achievements: Milestones and deliverables completed in the quarter
- Problems and improvements: Main problems encountered and solutions
- Next quarter's plan: Key work plan for the next quarter
Year-end Summary Generation
Generated according to the fixed template, including the following sections:
- Performance Achievement (1500-3000 words)
- Personal Growth (400-700 words)
- Growth Plan (400-700 words)
See the detailed template at templates/year-end.md
Step 6: Integrate with Planning Document (Applicable to Year-end Summaries)
If a planning document is provided:
- Extract key work points for the next year
- Identify resource requirements
- Sort out personal growth directions
Step 7: Output File
Output the generated report as a Markdown file, saved by default in the same directory as the weekly reports.
Important Notes
- Respect user guidelines: The user's provided key work scope and correction instructions have the highest priority
- Objective presentation: Avoid exaggerating achievements; use facts and data
- Highlight value: Emphasize the actual impact of work on business and team
- Clear structure: Use tables and lists to improve readability
- Weekly report deviation handling:
- Weekly reports may have omissions or inaccurate descriptions
- Make corrections and supplements according to user guidelines
- If in doubt, proactively ask the user for confirmation
Interaction Examples
Weekly Report Example (Based on Daily Records)
User: Help me generate this week's weekly report
Claude: Sure, I need some information to generate the weekly report:
1. Please provide the file path of this week's daily work records, or tell me what work you did this week
2. What is the time range of this week? (e.g., 2025.01.06 - 2025.01.10)
3. Who is the report recipient? (For salutation)
Weekly Report Example (Based on Oral Bullet Points)
User: Help me write a weekly report. I mainly did:
- AISE project document specification
- Apifox deployment and launch
- Code tracking MCP protocol development
Claude: Sure, I'll help you organize this into a weekly report. Please supplement the following information:
1. What were your work goals this week?
2. What is the progress of each task? (e.g., Completed, In progress 80%)
3. Are there any achievements, problems, or unfinished items to summarize?
4. Any reflections or improvement suggestions?
5. (Optional) Have you found any ineffective work or waste?
6. (Optional) Any progress in job promotion?
Monthly Report Example
User: Help me generate the December monthly report
Claude: Sure, I need some information to generate the monthly report:
1. Please provide the file path containing the December weekly reports
2. Which work do you want to highlight?
3. Which content needs to be downplayed or ignored?
Quarterly Report Example
User: Help me generate the Q4 quarterly report
Claude: Sure, I need some information to generate the quarterly report:
1. Please provide the file path containing Q4 (October-December) weekly reports
2. Which key projects need to be highlighted this quarter?
3. Which content needs to be downplayed or ignored?
Year-end Summary Example
User: Help me generate a year-end summary
Claude: Sure, I need some information to generate the year-end summary:
1. Please provide the file path of the weekly reports
2. Do you have a work plan document for next year?
3. Please tell me your position information and whether there was a role change during the year
4. Is there a reference format template?
5. Please provide some guidelines:
- Which work do you want to highlight?
- Which content needs to be downplayed or ignored?
- Are there any corrections needed in the weekly reports?
Common Issue Handling
Q: What if the weekly report has too much content and the summary is too long?
A: Filter according to the key scope specified in the user's guidelines. Secondary work can be merged or described concisely.
Q: What if the weekly report formats are inconsistent?
A: Try to identify key information (time, work content, results). Format differences do not affect content extraction.
Q: What if the user doesn't 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 reports, or ask the user for supplements.
Weekly Report Format Suggestions
To better support the generation of various reports, it is recommended that users write weekly reports in a standard format.
See templates/weekly-report.md