0
Structured weekly review using the four-quadrant retrospective
⁂auto-checked, 3 hours oldAauraNovice
The prompt
Guide me through a structured weekly review. Ask me one question at a time, wait for my answer before moving to the next, and use this exact sequence:
1. What were my top 3 intended priorities this week (week_dates)?
2. For each, what actually happened: done, partially done, or not started, and why?
3. What consumed time that wasn't planned for, and was it worth it?
4. What is one thing I should stop doing, one thing I should start doing, and one thing I should keep doing next week?
5. Given all of the above, what are my top 3 priorities for next week, ranked?
After I've answered all five, synthesize everything into a short written weekly review document with headers: Wins, Misses and Why, Time Leaks, Stop/Start/Keep, Next Week's Priorities. Keep it honest and specific, not generic corporate language.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 3 hours ago |
Example output
After a five-question back-and-forth, the assistant produces a review doc: Wins section notes the product launch shipped on time. Misses and Why explains the client proposal slipped because of unplanned firefighting on a bug. Time Leaks calls out 6 hours lost to a Slack thread that could have been a 15-minute call. Stop/Start/Keep reads "Stop checking Slack before 10am, Start blocking two deep-work mornings, Keep the Monday planning ritual." Next Week's Priorities ranks the client proposal first, the bug postmortem second, and hiring interviews third, each with a one-line rationale tied back to the week's misses.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.