AI Skill Report Card
Reflecting On Work Logs
YAML--- name: reflecting-on-work-logs description: Analyzes daily work logs to extract insights, assess progress, and plan tomorrow's priorities. Use when you need to review what you accomplished, identify patterns, and set focus for the next day. ---
Work Log Reflection and Planning
Quick Start
Input your raw work log:
Today I:
- Fixed 3 customer bugs in the payment system
- Had 2 hours of meetings (standup, planning)
- Started research on new authentication service
- Interrupted by urgent support ticket at 3pm
Get structured reflection:
- Accomplishments: 3 customer bugs resolved, authentication research initiated
- Time drains: 40% of day in meetings/interruptions
- Tomorrow's focus: Continue auth research, block calendar from 9-11am
- Insight: Need better interrupt handling process
Recommendation▾
Add a template or framework for the raw work log capture to help users know what level of detail to include
Workflow
Progress:
- Capture raw log - Dump everything you did/thought about
- Extract accomplishments - What actually moved forward?
- Identify energy patterns - When were you most/least effective?
- Spot time drains - What pulled you away from deep work?
- Surface insights - What patterns do you notice?
- Plan tomorrow - Pick 1-3 key priorities based on reflection
Recommendation▾
Include an example of weekly/monthly pattern analysis since it's mentioned in best practices but not demonstrated
Examples
Example 1: Input: "Spent morning debugging memory leak, afternoon in back-to-back meetings about Q4 planning, evening catching up on code reviews. Felt scattered and unproductive."
Output:
- Real work: Memory leak investigation, code reviews
- Energy killer: Meeting overload broke flow state
- Pattern: Deep technical work best in morning
- Tomorrow: Block 9am-12pm for focused debugging, batch meetings after 2pm
- Reflection: Need to protect morning focus time
Example 2: Input: "Wrote first draft of proposal, client called with scope changes, updated timeline, team member asked for help with deployment issue."
Output:
- Progress: Proposal draft completed despite interruptions
- Strength: Good at context switching and helping others
- Risk: Scope creep from client changes
- Tomorrow: Revise proposal with new scope, document deployment process to reduce future interrupts
- Insight: Need clearer boundaries for client change requests
Recommendation▾
Provide a specific time-boxing template for tomorrow's planning (e.g., calendar blocking format)
Best Practices
Honest assessment: Include failures, frustrations, and time wasters Pattern recognition: Look for weekly/monthly trends, not just daily events Specific priorities: "Finish user auth" not "work on project" Energy mapping: Note when you're sharpest vs. when you drag Quick capture: Use voice memos, bullet points, whatever flows naturally
Common Pitfalls
- Over-planning tomorrow: Max 3 priorities, account for inevitable interrupts
- All positive spin: Missing growth opportunities by ignoring struggles
- No time boundaries: "I'll work on X" vs. "I'll work on X from 9-11am"
- Skipping the why: Note why something worked/didn't work, not just what happened
- Perfect logs: Better to reflect on messy reality than clean fiction