---
name: weekly-review
description: A weekly check-in workflow that reviews the past week, scans what's ahead, and produces a summary with priorities.
triggers:
  - weekly review
  - how'd my week go
  - plan my week
  - Sunday review
---

# Weekly Review

Step back, look at the week, and plan the next one.

## When to Use

Run this once a week — Sunday evening, Monday morning, or whenever works for your rhythm.

## Instructions

### Step 1 — Gather
1. Check this week's calendar events (if calendar MCP is connected).
2. Review completed tasks or projects from the week.
3. Scan any notes, journal entries, or captured items from the past seven days.

### Step 2 — Review
1. Summarize what happened this week: key events, completed work, progress made.
2. Identify what's still open: tasks that didn't get finished, items that slipped.
3. Flag anything overdue or time-sensitive.

### Step 3 — Reflect
Ask the user:
- How did the week go overall?
- What went well?
- What needs attention next week?
- Anything you want to change or adjust?

### Step 4 — Output
Produce a formatted weekly summary:

**Weekly Review — [Date Range]**

**What Happened**
[Key events, accomplishments, completed work.]

**Still Open**
[Unfinished items, slipped tasks, things that need attention.]

**Next Week**
[Upcoming calendar events, deadlines, priorities.]

**Reflections**
[The user's notes on how the week went and what to adjust.]

## Customization Ideas

This is a starter weekly review. As you use it, consider adding:
- Role-based review (how did each area of your life/work get attention?)
- Goal tracking (progress toward monthly or quarterly goals)
- A journaling step that gets saved to a long-term record
- Automated data gathering from connected tools

The assembler in Video 7 will help you customize this to your actual workflow and connected tools.

## Rules

- The reflection step is conversational — ask questions and let the user respond. Don't skip it or auto-fill it.
- Keep the output scannable. Short lines, clear sections.
- If data sources aren't connected, work with what's available. A review based on the user's verbal summary is still valuable.
- Save the output to the workspace so it becomes a record over time.

---

*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 7 via the assembler.*