Weekly Report Auto-Generation

Skill Overview

Weekly reports are the most common form of work reporting in the workplace, yet many people spend considerable time writing them without capturing the key points. This skill helps you quickly generate a well-structured, focused weekly report based on your week's work records, meeting minutes, project progress, and other materials.

Input Requirements

When using this skill, please prepare the following information:

• Work Completed This Week: List the main tasks you handled this week, including project names, specific items, and completion status
• Meeting Minutes or Communication Records: Important meeting content from the week and decisions reached
• Problems and Obstacles Encountered: Difficulties and risk points in work, and current resolution status
• Next Week's Work Plan: Already-confirmed action items for next week and priority levels
• Resources Needing Coordination: Cross-department collaboration needs or support required from management

The more detailed the information provided, the higher the quality of the generated report. It's recommended to develop a habit of simple daily recording so that weekly summary is much easier.

Output Format

The generated weekly report will include the following standard structure:

1. Weekly Work Overview: Summarize core deliverables of the week in 2-3 sentences
2. Key Work Progress: Organized by project or module, listing completion status and key results
3. Problems and Risks: Issues encountered and their impact scope
4. Data and Results: Quantified work results, such as completion rate, bugs fixed, etc.
5. Next Week's Plan: Next week's action items arranged by priority
6. Support Needed: Clearly list items requiring coordination or decisions

Usage Tips

• Highlight results rather than process: Reports should focus on "what was accomplished" rather than "what was done," describing work in result-oriented language
• Make good use of data quantification: Whenever possible, use specific numbers to illustrate work output. "Completed development for 5 requirements" is more convincing than "promoted project development"
• Control length: Weekly reports are not logs of daily activities; keep to one page so leaders can read it in 2 minutes
• Maintain consistency: Use the same format and structure each week for easy comparison and review
• Prepare materials in advance: Recommend spending 1 minute daily recording key work so weekly summaries are much more efficient

Applicable Scenarios

• Quickly generate this week's work summary Friday afternoon
• Material organization for project phase-based reporting
• Work record archiving for probationary employees
• Asynchronous communication reporting for remote work teams