borghei/Claude-Skills / personal-productivity/weekly-review
weekly-review
VerifiedTurn a week's wins, learnings, blockers and OKR progress, gathered by hand from your calendar, tasks and journal, into a structured review with next-week priorities. Use for a Friday/Sunday weekly review, GTD review, or OKR check-in.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.0 KB |
| assets/weekly_review_input.json | config | 2.5 KB |
| references/weekly_review_methodology.md | markdown | 5.3 KB |
| scripts/weekly_review_synthesizer.py | script | 4.0 KB |
references/weekly_review_methodology.md
View on GitHub# Weekly Review Methodology
The weekly review is the highest-leverage personal-effectiveness habit you can adopt. It's where you convert week-to-week task execution into season-long compounding.
---
## The Core Idea
Without a weekly review:
- Tasks pile up; you never decide what to drop
- OKRs drift quietly until the quarter ends
- You repeat avoidable mistakes
- You over-commit because you never see the full week ahead
A weekly review is where you make the meta-decisions that the moment-to-moment task layer can't.
---
## The Standard Components
### Inputs to gather (5-10 min)
- Calendar from the past week (what actually happened)
- Task list / inbox state (what's open, what's stuck)
- Email / Slack scan (anything pending)
- Journal entries / notes from the week
- OKR / goal scoreboard
### Components to capture (15-20 min)
**Wins** — 3-5 things that went well. Specific. Names and numbers.
**Learnings** — 1-3 things you learned, especially things you didn't want to. What surprised you?
**Blockers / risks** — 1-3 things that could derail next week. Each with an owner (often you) and a mitigation.
**OKR / goal progress** — for each active OKR, where you are and whether the trend supports closing the gap.
**Next-week priorities** — top 3 priorities. Not 10. Not 5. Three.
**Open loops to close** — small annoyances accumulating attention.
**Things to actively decline** — meetings, asks, distractions you'll say no to.
**Journal note** — 1-2 sentences for your future self.
### Self-coach prompts (5 min)
- What did I avoid this week that I shouldn't have?
- What am I telling myself I'm too busy for that I'm actually just avoiding?
- What would I do differently if I started this week over?
- What is the single most important thing for next week?
---
## The GTD Weekly Review
David Allen's classic version:
1. **Get clear** — collect all loose papers and inputs; process to zero
2. **Get current** — review action lists, calendar, projects, areas of focus
3. **Get creative** — review someday/maybe; capture new ideas
Allen's GTD review is more comprehensive than what most people need; the structure here is a lighter weight version. If GTD resonates, do the full thing.
---
## OKR Check-In
If you use OKRs, the weekly review is the right rhythm for OKR check-ins:
- For each KR, current progress vs. trajectory needed for end-of-quarter
- Identify any KR that has drifted off-track
- Decide: invest more, descope, or accept the miss
Weekly is signal; quarterly is the action moment. Don't churn the OKRs themselves week-to-week.
---
## Cadence
Most people do a weekly review on Friday afternoon or Sunday evening. Both work; consistency matters more than which.
**Friday afternoon:**
- Pro: while context is fresh
- Pro: you go into weekend with a clean mental ledger
- Con: end-of-week energy may be low
**Sunday evening:**
- Pro: better energy after rest
- Pro: helps prime Monday
- Con: weekend brain is slower; some details are foggy
Either works. Pick one. Defend the time.
---
## Length
- **Target:** 30-45 minutes
- **Maximum:** 60 minutes
- **Floor:** 20 minutes (still better than skipping)
If your reviews are taking 90 minutes, you're trying to do too much in the review. Move some of it (deep planning, OKR refresh) to a separate monthly or quarterly session.
---
## Quarterly Pattern Review
Save your weekly reviews in a single folder. Quarterly:
1. Read all 12-13 weeks back-to-back
2. Look for patterns:
- Recurring blockers you keep mentioning but never fix
- Energy patterns (which weeks were great? what was different?)
- OKR drift (which quarters did you over-commit?)
- Avoidance patterns (what do you keep promising to do "next week"?)
3. Adjust:
- Re-baseline OKRs if structurally over-committed
- Schedule a single "fix the recurring blocker" deep work session
- Decline the meeting category that's draining energy
This compounding-pattern review is where the long-term value of weekly reviews shows up.
---
## Common Pitfalls
- **Skipping when busy.** The weeks you most need to review are the weeks you skip. Don't.
- **Over-formatting.** Pretty reviews you don't read are worse than ugly ones you do.
- **No wins captured.** Always note wins, even when the week was hard. Pattern of wins matters.
- **No declines captured.** A weekly review without explicit "no" is incomplete.
- **Inputs without outputs.** Reflection without a next-week priority list is performance theater.
- **OKR thrash.** Weekly is for check-in, not re-baselining. Resist the urge to change the targets.
- **Brain dumping into the review instead of triaging.** The review consolidates; doesn't replace your task list.
---
## When to Skip
Almost never. But:
- You're on real vacation (no work check-in) — skip the review of those weeks
- Major personal event (illness, family, etc.) — skip and resume
- The act of reviewing is causing more anxiety than benefit — see a coach / therapist; the review isn't the problem
---
## Resources
- **Getting Things Done** by David Allen — the canonical reference
- **Cal Newport's blog** — deep work + weekly review intersection
- **Tiago Forte's PARA / Building a Second Brain** — note-taking layer below the review
- **Andy Matuschak / Maggie Appleton** — note-taking and reflection essays
- Various weekly-review templates published online — useful as starting points; customize over 4-6 weeks
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |