The Weekly Review That Writes Itself
Scattered updates from five people become one coherent business review.
Five people send five formats. Reading them takes an hour and you still cannot see the pattern across them.
That is the gap this drop closes. It is a operations skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Managing directors running multiple ventures or departments.
How it works
The skill file does five things, in this order.
1. Collect in any format. Voice notes, WhatsApp, bullet lists, half sentences. All fine.
2. Normalise to one shape. Shipped, blocked, at risk, and needs a decision from you.
3. Find the cross-cutting theme. Three people blocked on the same thing is the actual finding.
4. Compare against last week. What was going to be done and was not. Every single week.
5. Produce your decision list. The three things only you can unblock, ranked by cost of delay.
What comes back
A one-page review, a repeated-blocker list, and three decisions ranked by cost of delay.
The mistake to avoid
Give it last week's review every time. Tracking what slipped week over week is the entire value, and no update format captures it on its own.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Build this week's business review from these raw updates.
<last_week_review>{paste}</last_week_review>
<this_week_updates>{paste all, any format}</this_week_updates>
1. SHIPPED, what actually completed, per area.
2. SLIPPED, items promised in last week's review that did not land. Include
how many consecutive weeks each has slipped. This section is mandatory even
if nobody mentioned it.
3. BLOCKED, with who is blocking and since when.
4. CROSS-CUTTING, patterns appearing in three or more updates. This is the
section I care most about.
5. YOUR DECISIONS, maximum three, ranked by cost of delay, each with the
options and your recommendation.
Do not soften. If an area went quiet, say it went quiet.