weekly-summary

name	weekly-summary
description	Summarize a week of daily notes, identifying key themes, accomplishments, people engaged with, and ongoing action items. Use when the user asks for a weekly review or summary of the past week.

Weekly Summary Skill

Generate a comprehensive summary of a week's worth of daily notes.

When to Use

Use this skill when:

• User asks "Summarize this week" or "What happened this week?"
• User requests a weekly review
• User asks for accomplishments or progress over the week
• End of week review requested

Instructions

1. Determine Date Range

If user specifies dates: use those dates.

If user says "this week": calculate the current week (Monday-Sunday or user's preferred week start).

If user says "last week": calculate the previous week.

Default: Use the most recent 7 days including today.

2. Read Daily Notes

For each date in the range:

• Read notes/YYYY-MM-DD.md
• If a file doesn't exist, note it but continue with other days
• Collect all content from all available daily notes

3. Aggregate Information

Across all notes, identify:

Major Themes:

• What were the main focus areas?
• What projects or topics appeared most?
• Any patterns in activities?

Accomplishments:

• Completed tasks (checkbox items marked [x])
• Milestones reached
• Decisions made
• Problems solved

People Engaged:

• List all people mentioned across all notes
• Count frequency of mentions
• Note context of significant interactions

Ongoing Work:

• Open action items (checkbox items marked [ ])
• Recurring themes or concerns
• Work in progress

Key Decisions:

• Important choices made
• Direction changes
• Commitments

Insights & Reflections:

• Notable learnings or observations
• Personal growth or realizations
• Ideas generated

4. Generate Summary

Format the output as:

# Weekly Summary: [Date Range]

**Period**: [Start Date] to [End Date]
**Notes Available**: [X] of [Y] days

## Overview

[2-3 sentence high-level summary of the week]

## Major Themes

- [Theme 1]: [Brief description]
- [Theme 2]: [Brief description]

## Key Accomplishments

- [Accomplishment 1]
- [Accomplishment 2]
- [Accomplishment 3]

## People Engaged

- [Person 1]: [Context - e.g., "3 meetings, discussed project X"]
- [Person 2]: [Context]

## Important Decisions

- [Decision 1]
- [Decision 2]

## Ongoing Action Items

- [ ] [Open task 1]
- [ ] [Open task 2]

## Insights & Learnings

- [Insight 1]
- [Insight 2]

## Next Week Focus

[1-2 sentences suggesting priorities based on the week's content]

Omit sections that are empty.

5. Keep it Focused

• Aim for 400-600 words total
• Highlight the most significant items
• Group similar items together
• Don't list every small detail
• Focus on patterns and themes over individual events

Examples

Input

Multiple daily notes from Feb 3-9, 2026 containing:

• Several meetings with project team
• Completed design phase
• Decision on new architecture
• Multiple interactions with Jane and Bob
• Several open action items

Output

# Weekly Summary: February 3-9, 2026

**Period**: 2026-02-03 to 2026-02-09
**Notes Available**: 5 of 7 days

## Overview

Strong progress on project redesign with completion of design phase and key architecture decisions. Heavy collaboration week with multiple team meetings and stakeholder discussions.

## Major Themes

- **Project Redesign**: Core focus of the week with design completion and architecture planning
- **Team Collaboration**: Daily standups and several ad-hoc meetings
- **Decision Making**: Critical technical and strategic choices made

## Key Accomplishments

- Completed full design review and received approval
- Selected Option B for system architecture after thorough analysis
- Resolved three major technical blockers
- Shipped prototype to staging environment
- Documented new API specifications

## People Engaged

- Jane (5 interactions): Project proposal reviews, feedback sessions, planning discussions
- Bob (3 interactions): Design reviews, architecture decisions, technical discussions
- Sarah (2 interactions): Stakeholder updates, budget approval

## Important Decisions

- Committed to Option B architecture (more scalable, better long-term fit)
- Decided to push Phase 2 to next quarter to ensure quality
- Approved budget increase for additional tooling

## Ongoing Action Items

- [ ] Send final proposal to Jane by Feb 12
- [ ] Schedule Q1 planning meeting with full team
- [ ] Document architecture decision rationale
- [ ] Follow up with Bob on deployment timeline
- [ ] Review vendor contracts

## Insights & Learnings

- Early stakeholder involvement prevented scope creep
- Architecture decision taking extra time paid off in clarity
- Team collaboration improving with structured daily check-ins

## Next Week Focus

Finalize proposal submission and begin implementation phase. Schedule Q1 planning to set clear milestones for the quarter.

Edge Cases

Few or No Notes: If only 1-2 notes exist for the week, provide whatever summary is possible and note the limited data.

Very Active Week: If there's extensive content, focus on the highest-impact items and mention "many additional activities not listed here."

Custom Date Ranges: Adapt to any date range requested, not just Monday-Sunday weeks.

Tips

• Look for patterns across multiple days
• Emphasize accomplishments and forward progress
• People mentioned frequently are likely key collaborators
• Group related action items together
• The summary should give a sense of momentum and direction
• Compare early week vs. late week to show progress
• Note any shifts in focus or priorities during the week