A Claude skill that runs your weekly review from your real data and plans next week
It checks last week's commitments against your numbers, names what you keep putting off and sets next week's priorities against the one metric you choose. Free to download.
Instant download of this one skill. No spam.
Weekly retro/weekly-retro
Using the weekly-retro skill
Notion Last week: 3 commitments, 2 kept
Stripe £14,200 booked, up from £11,400
Xero 2 invoices overdue, £6,300
Google Calendar 11 hours in meetings, 0 on partners
Granola 6 calls, 2 partners awaiting a replyRevenue's up, but partner outreach has come up three weeks running. Your calendar gave it no time, and two partners are still waiting on you.
What did you avoid this week?
The partner emails, again
Third week running, so let's shrink it.
- Reply to the two waiting partners
- Chase the two overdue invoices
Website redesign: it doesn't move revenue
Your commitment: both replies sent by Tuesday at noon. I'll check that first next Friday.
Every weekly retro starts from last week's commitments and ends with next week's
Each Friday the skill reads three things, runs four steps and hands you three. Next Friday it opens by checking what you committed to this week.
What it reads
- Your goal and one metricSet on the first run, with the number that most drives it.
- Last week's retroWhat you said mattered, and what you committed to.
- Anything you connectOptional: your calendar, task list or wherever the number lives.
What it does every Friday
- Check last weekDid the commitments happen? What keeps coming back without moving?
- Bring the numbersYour metric against target, and whether your hours matched your priorities.
- Interview youFive questions, one at a time, then it plays back what it heard.
- Plan next weekEvery item scored on whether it moves the metric.
What you get
- This week's retroSaved where you keep your work: a folder, a Notion page, a Google Doc.
- Two or three priority betsEach tied to the metric, each with a next action.
- One checkable commitmentA day and a time, or a result next Friday can verify.
Any role can run this retro: only the metric changes
- Founder
- Revenue booked
- Salesperson
- Qualified meetings
- Marketer
- Sign-ups from content
- Engineer
- Features shipped
- Manager
- Decisions unblocked
- Recruiter
- Roles filled
- Consultant
- Billable hours
- Writer
- Words drafted
Can't name your metric yet? It helps you draft one and makes agreeing it next week's priority.
The five weekly reflection questions it asks at the end of every week
- What was your biggest win?
- What drained you?
- What did you avoid?
- What's genuinely stuck?
- Honestly, how do you feel about your progress on the goal?
When an answer matches something you have dodged before, it says so on the spot: “you've named this three weeks running and not moved it. What's actually going on?” By the third time, it stops re-listing the item and changes the plan: a smaller first step, a fixed slot or a date someone else will check.
The weekly review template it fills in for you
You talk, it writes. Before saving anything it plays back what it heard so you can correct it, then files the retro in your retro home as a document you can scan in a minute next Friday.
It never pads a thin section with things you did not say, and it records this week's number next to last week's so the trend stays visible.
Example retro: a marketer
The retro skill installs in Claude, Claude Code, Codex or ChatGPT in two minutes
- Claude
In claude.ai or the desktop app, go to Customize, then Skills, click +, choose Upload a skill and upload weekly-retro.zip as it is. It then appears in Claude Code too, on the same account.
Claude CodeUnzip it into ~/.claude/skills/, so the file ends up at ~/.claude/skills/weekly-retro/SKILL.md.
CodexUnzip it into ~/.agents/skills/, then start a new session.
ChatGPT for WorkGo to Skills, then Create, then Upload from your computer, and upload the zip. Business, Enterprise, Healthcare and Edu only, and your admin has to allow uploads.
Then type /weekly-retro at the end of your week. To make it run on its own, see the last question below.
Get the weekly retro skill free
Add your email and the download unlocks here straight away.
Instant download of this one skill. No spam.
Questions people ask before installing the weekly retro skill
What's the difference between a weekly review and a weekly retro?
A weekly review usually means tidying your lists and calendar. A weekly retrospective, or retro, borrows from team retros: what went well, what did not and what changes next week. This skill does the retro and keeps it tied to one goal, so the review part is measured against a number rather than a feeling.
How is it different from a GTD weekly review?
The Getting Things Done weekly review is about getting every inbox and list back to clear. This one is about whether your week moved the one metric you care about, and about holding you to what you said last Friday. They work well together: clear the lists, then run the retro.
Can Claude be my accountability partner?
That is the job this skill gives it. It reads back what you committed to last week, names anything you have put off two or three weeks running, and asks for a commitment next week can check, such as a day and a time, rather than "I'll find time".
Do I need to connect my calendar or task list?
No. With nothing connected it runs the simple version: the accountability check, the interview and next week's plan. Connect your calendar, task list or the place your key number lives and it leads with real figures instead of your memory of the week.
Where does it keep my retros?
Wherever you choose on the first run: a local folder, a single file, a Notion page or a Google Doc. It writes your goal, its setup notes and every retro there, and reads them back the next week. With no home at all it gives you the retro in the chat and tells you to save it.
What happens the first time I run it?
It sets you up rather than holding you to anything: where to keep the retros, who reads them, the one metric you want to move and what it can connect to. It never invents a history, so pattern call-outs only start once there are past retros to compare.
Can I share the retro with my manager?
Yes. It keeps a private version and a shared one, asks which side anything sensitive belongs on, and reads the shared version back to you before it saves or sends it.
How do I make it run every Friday?
In Cowork, set a Scheduled Task. In Claude Code, use a scheduled task in the desktop app or just say "weekly retro" on a Friday. Routines run in the cloud and cannot see skills installed on your own machine, so they will not run a locally installed copy.
Pair it with the workspace review skill: the retro reviews your week, and the workspace review checks your Claude setup on the same Friday.
For the bigger picture, the monthly review skill steps back from the weeks to your long-term goal and sets next month's goals.