Chloe Adams·
Built a weekly review generator that turns my scattered Notion captures into next week's plan in about four minutes. Sunday evenings are calm now.
Processes a raw brain-dump of the week into a structured review plus a realistic plan for the coming week.
Weekly Review & Next-Week Plan Generator
Act as my weekly review facilitator. I will paste an unedited dump of everything from my week: completed tasks, half-done items, notes, complaints, wins, and stray ideas.
Process it in this order:
**Part 1 — Review of the past week**
- Wins: 3-5 things that actually moved {{main_goal}} forward. Ignore busywork.
- Incomplete: list every unfinished item and classify each as Carry Over / Delegate / Delete / Someday. Be aggressive with Delete — if it has been carried over twice already or has no owner and no deadline, recommend deletion and say why.
- Friction log: recurring annoyances that cost me time this week. For each, suggest one concrete system fix (template, automation, calendar block, or saying no).
**Part 2 — Plan for next week**
- Pick a maximum of 3 priorities for the week, derived from Carry Over items plus {{upcoming_commitments}}. State the "done means" condition for each in one sentence.
- Draft a realistic time-block outline for the week: deep work blocks in the morning, meetings and shallow work after {{focus_cutoff_time}}, and at least one completely empty buffer block.
- Flag any day that is overloaded (more than 6 hours of planned work) and propose what to move.
Tone: direct, practical, zero motivational filler. Output everything as markdown checklists I can paste straight into Notion.
Here is my dump:
{{weekly_dump}}
Ergebnisse
## Weekly Review — Week 26
### Wins
- [x] Shipped the client onboarding template — directly advances the "productize services" goal
- [x] Migrated task database to the new schema (unblocks automation work)
- [x] Said no to the podcast request — protected 4h of deep work
### Incomplete Items
| Item | Verdict | Why |
|---|---|---|
| Write automation docs | **Carry Over** | Blocks two client handoffs |
| Redesign personal site | **Someday** | No deadline, no dependency, third week on the list |
| Reconcile Q2 invoices | **Delegate** | Bookkeeper can do this; send by Tuesday |
| "Research CRM options" | **Delete** | Carried over twice, no decision criteria defined. Re-add only with a concrete trigger |
### Friction Log
1. **Re-explaining project status in Slack** (~45 min/week) → Fix: pin a weekly status template, update every Friday at 16:00.
2. **Context-switching between client workspaces** → Fix: batch client A to Mon/Tue, client B to Wed/Thu.
3. **Meeting prep scramble** → Fix: 15-min prep block auto-scheduled before every external call.
## Plan — Week 27
### Priorities (max 3)
1. **Automation docs shipped** — done means: published in the client portal and linked in both handoff emails.
2. **Client B kickoff prepared** — done means: agenda sent, workspace set up, contract countersigned.
3. **Q2 admin closed** — done means: invoices delegated, expenses filed.
### Time-Block Outline
- **Mon:** 08:30-11:30 deep work (docs) · 13:00 client A calls
- **Tue:** 08:30-11:30 deep work (docs) · 14:00 delegate invoices
- **Wed:** 08:30-11:00 kickoff prep · 13:00 client B
- **Thu:** 08:30-11:30 buffer — deliberately empty
- **Fri:** admin, weekly review, 16:00 status update
⚠️ **Overload flag:** Wednesday holds 6.5h of planned work. Move workspace setup to Thursday's buffer.
Modell: Claude Sonnet 4.6
34 Likes21 SavesScore: 24
2 Kommentare
Sofia Almeida·
The Delete rule for twice-carried-over items is brutal and correct. Adopted.
Ethan Reed·
Empty buffer block as a first-class citizen — yes. Most planning templates pretend Thursday doesn't happen.