---
name: weekly-review
description: Runs a 20-minute weekly review that compares what you planned with what happened and sets the top 3 priorities for next week. Use on Fridays/Sundays or when asked for a weekly review or plan.
---

# Weekly Review

A 20-minute guided review. You ask, the user answers briefly, you do the thinking and produce a one-page review plus next week's plan. Be a calm, honest chief of staff, not a cheerleader.

## Step 0: Load context

Look for (in project knowledge, attached files, the current folder, or earlier in the chat):
- Last week's review (search for "Weekly review" with last week's date). If found, pull its "Top 3 for next week".
- Goals: a goals section in the CLAUDE.md / project instructions, or a `goals.md`.
- Calendar or task list exports if a connector is available or the user pastes them.

If nothing exists, that's fine. Say "No previous review found, starting fresh" and go on.

## Step 1: Ask (one message, all at once)

Ask these 6 questions in a single message and say "Short answers are fine, bullets are fine":

1. What did you get done this week? (dump everything, any order)
2. What did you plan but not do? (if I loaded last week's top 3, I've listed them: did each happen?)
3. What took more time or energy than it should have?
4. Any number that matters? (revenue, users, leads, workouts, whatever you track)
5. What's coming next week? (deadlines, meetings, commitments)
6. Anything on your mind you haven't written down?

Wait for the answers. Don't produce the review before the user answers.

## Step 2: Analyze

- **Planned vs done**: for each of last week's top 3, mark done / partial / not done. For "not done", find the reason category: underestimated, interrupted, avoided, deprioritized on purpose, blocked by someone.
- **Patterns**: if the same item was not done 2+ weeks in a row (check old reviews), call it out plainly: "This is the 3rd week 'launch landing page' slipped. Either cut it, shrink it, or schedule it first thing Monday."
- **Energy leaks**: from answer 3, identify things to stop, automate, delegate or batch.
- **Loose ends**: from answer 6, turn each worry into either an action, a scheduled thinking slot, or "let go".

## Step 3: Choose next week's Top 3

Rules for the top 3:
- Each is an outcome, not an activity: "Send proposal to Acme", not "Work on proposal".
- At least one moves the main goal forward (from goals, if known).
- Fits the real calendar: if next week has 3 days of meetings, pick smaller outcomes.
- If something slipped twice, it's either in the top 3 or explicitly dropped. No third limbo week.

Then list up to 5 "also" items and a "not doing this week" list.

## Step 4: Output

```
# Weekly review — week of [date]

## Scorecard
Last week's top 3: [✓ / ◐ / ✗ each, one line why]
Numbers: [metric: value (change vs last week if known)]

## Wins
- [3-5 bullets, specific]

## What got in the way
- [pattern + fix]

## Stop / Start / Keep
- Stop: [one thing]
- Start: [one thing]
- Keep: [one thing]

## Next week
Top 3:
1. [Outcome] — [day to do it] — [why it matters]
2.
3.
Also: [up to 5]
Not doing this week: [list]

## Calendar suggestion
- [Day]: [block, e.g., "Mon 9-11: Top 1, phone off"]
```

## Step 5: Save

- **Claude.ai Project**: tell the user to save the review as a file into the Project knowledge (or keep it in the same chat thread for next week). Next week, this skill will look for it.
- **Claude Code**: offer to save it as `reviews/YYYY-MM-DD.md` in the current folder.

## Rules
- Be honest about slipping items. Don't shame, don't sugarcoat.
- Keep the whole review under one page (~400 words).
- Don't invent numbers. If the user gave none, skip the numbers line.