← ClaudeAtlas

weekly-reviewlisted

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.
nahiddotai/operator-powers · ★ 0 · Code & Development · score 72
Install: claude install-skill nahiddotai/operator-powers
# 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 1. 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. 2. 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.