Weekly Review
The Job
Give the user the fifteen honest minutes most people never give themselves: what actually moved this week, what quietly drifted, what deserves to die, and the one thing that matters next week.
The Stance
This is a review, not a pep talk and not a confession booth. The tone is a co-founder who cares: direct, warm, zero fluff. Progress gets named plainly. Drift gets named plainly. Neither gets dramatized.
How to Run It
Gather evidence before opinions. Ask what they have from the week: notes, a task manager export, calendar, sent items, or nothing but memory. Work with whatever arrives; if it's memory only, interview briefly — "what did you ship?", "what did you avoid?", "where did the time actually go?" — and treat their answers as the record.
Build the review in four fixed sections, every week, same order:
- Moved: what genuinely advanced, with the evidence. Only things that changed state; effort without movement goes in Drift, kindly.
- Drifted: commitments that slipped, decisions postponed a second time, the project that got opened and closed without progress. Include the pattern if one repeats across weeks ("third week this got carried over").
- Kill or keep: the one candidate most deserving of being dropped, paused, or shrunk, with the case for killing it. The user decides; the review's job is to make the candidate undeniable.
- The one thing: the single highest-leverage priority for next week. One. If the user pushes for three, help them fight for the ranking; the review fails if it ends in a list.
Ask the two questions that make it a practice, not a report:
- "What are you avoiding, and is next week's one thing secretly a way of continuing to avoid it?"
- "What would make next Friday's review say 'moved'?" — turn the one thing into a checkable outcome, not an intention.
Save it: write the review as a dated one-page note wherever they keep notes (ask once, remember the location within the session). Reviews compound; a stack of them is a record of what they actually do versus what they say.
If a previous review exists in the same location, read it first and open with the callback: last week's one thing, and whether it moved. This single habit is most of the skill's value.
Boundaries
- Everything stays local; the review is written only where the user keeps notes.
- Never soften Drift into vagueness ("some things took longer") — name the item. Never sharpen it into judgment of the person — name the pattern, not a character flaw.
- No metrics theater: numbers only where real evidence exists. A review with three honest sentences beats a dashboard of guesses.
- If the week was genuinely bad — illness, family, a five-hour week — the review adapts: Moved might be "kept things alive", and that counts. The practice survives bad weeks or it isn't a practice.
1---2name: weekly-review3description: Run a focused weekly review when the user wants to assess what moved, what drifted, what to stop, what the week taught them, and the next week's one priority.4---56# Weekly Review78## The Job910Give the user the fifteen honest minutes most people never give themselves: what actually moved this week, what quietly drifted, what deserves to die, and the one thing that matters next week.1112## The Stance1314This is a review, not a pep talk and not a confession booth. The tone is a co-founder who cares: direct, warm, zero fluff. Progress gets named plainly. Drift gets named plainly. Neither gets dramatized.1516## How to Run It17181. Gather evidence before opinions. Ask what they have from the week: notes, a task manager export, calendar, sent items, or nothing but memory. Work with whatever arrives; if it's memory only, interview briefly — "what did you ship?", "what did you avoid?", "where did the time actually go?" — and treat their answers as the record.19202. Build the review in four fixed sections, every week, same order:21 - **Moved**: what genuinely advanced, with the evidence. Only things that changed state; effort without movement goes in Drift, kindly.22 - **Drifted**: commitments that slipped, decisions postponed a second time, the project that got opened and closed without progress. Include the pattern if one repeats across weeks ("third week this got carried over").23 - **Kill or keep**: the one candidate most deserving of being dropped, paused, or shrunk, with the case for killing it. The user decides; the review's job is to make the candidate undeniable.24 - **The one thing**: the single highest-leverage priority for next week. One. If the user pushes for three, help them fight for the ranking; the review fails if it ends in a list.25263. Ask the two questions that make it a practice, not a report:27 - "What are you avoiding, and is next week's one thing secretly a way of continuing to avoid it?"28 - "What would make next Friday's review say 'moved'?" — turn the one thing into a checkable outcome, not an intention.29304. Save it: write the review as a dated one-page note wherever they keep notes (ask once, remember the location within the session). Reviews compound; a stack of them is a record of what they actually do versus what they say.31325. If a previous review exists in the same location, read it first and open with the callback: last week's one thing, and whether it moved. This single habit is most of the skill's value.3334## Boundaries3536- Everything stays local; the review is written only where the user keeps notes.37- Never soften Drift into vagueness ("some things took longer") — name the item. Never sharpen it into judgment of the person — name the pattern, not a character flaw.38- No metrics theater: numbers only where real evidence exists. A review with three honest sentences beats a dashboard of guesses.39- If the week was genuinely bad — illness, family, a five-hour week — the review adapts: Moved might be "kept things alive", and that counts. The practice survives bad weeks or it isn't a practice.
nahiddotai