Productivity

Weekly Review and Next-Week Plan Generator

Turn a messy week of notes into a GTD-style weekly review, a next-week plan with three priorities, and a shutdown checklist you can run in 30 minutes.

0.0
0Reviews
P
August 24, 2026

Prompt

Act as an operations coach who has run weekly reviews with founders and ICs. Close last week. Open next week. Do not invent meetings, tasks, or feelings that were not in Inputs. Prefer fewer commitments.

Inputs:
- Role and hours: [Job, typical hours, time zone]
- Week just ended: [Dates]
- Wins: [Done work, even small]
- Open loops: [Tasks, waiting-on, worries]
- Calendar residue: [Meetings that overran, holes]
- Energy and health: [Sleep, focus, constraints]
- Personal non-work: [Family, errands, rest]
- Next week hard landscape: [Fixed meetings, travel, deadlines]
- Capacity: [Deep-work hours I actually have]
- Tools: [Calendar, task app]
- Goal of the review: [Calm / catch-up / ambitious]

Generate:
1. Closeout: 8-10 sentences. What actually moved. What was theater. One sentence on energy, labeled as inference if Inputs are thin.
2. Inbox zero for the mind: Sort Open loops into Done / Do next week / Waiting on (name a person) / Someday / Delete. No item left unsorted.
3. Three priorities for next week: Outcome language, not a 20-line to-do. Each: done-when test, first physical next action, a time block suggestion, what you will say no to so it fits.
4. Next-week plan: Day-by-day from the hard landscape. Put deep work where Capacity lives. Protect one recovery block. Flag any day that is already over capacity and cut.
5. Waiting-on list: Person, ask, date you will nudge. Scripts of 2 sentences max.
6. Metrics I will not track: 4 vanity measures to ignore this week.
7. 30-minute run sheet: Minute-by-minute so I can do this again next Friday without you.
8. Shutdown phrase: One line I can say when the week is closed.

Constraints:
- If Capacity is missing, assume 10 deep-work hours and say so.
- Do not add habits I did not ask for. Do not invent a 5am routine.
- No em dashes. No "crush it." No 40-item task dump.
- Honor health constraints. If energy is low, cut the plan, do not pep-talk.
- Write for a tired person on Friday at 4pm.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Role and hours: product manager, ~45 hours, America/New_York
Week just ended: Mon Aug 17 to Fri Aug 21, 2026
Wins: shipped guided setup v1 notes to eng, ran 3 customer calls, wrote the July board memo
Open loops: TTFV dashboard still not live, AE job description half-done, waiting on Maya for churn list, dentist reschedule, idea for a pricing experiment I do not want to lose
Calendar residue: two 90-min calls ran long; Wednesday afternoon was empty and I filled it with Slack
Energy and health: slept 6 hours, good focus Tue/Thu, fried Friday
Personal non-work: partner's birthday dinner Thursday 7pm, groceries
Next week hard landscape: Mon all-hands 10-11, Tue-Wed onsite at First Prairie (travel Mon 3pm, back Wed 9pm), Fri board packet due 3pm
Capacity: maybe 8 deep-work hours if I protect them; onsite days are mostly meetings
Tools: Google Calendar, Linear
Goal of the review: catch-up, not ambitious. I will be onsite.

Example Output

1. Closeout
Guided setup notes, three customer calls, and the July memo are real. The empty Wednesday you poured into Slack was theater. TTFV dashboard and the AE JD did not move. Energy: six hours of sleep, two good focus days, Friday fried. Inference: next week cannot be a catch-up fantasy on top of an onsite.

2. Inbox zero
Done: setup notes, three calls, board memo.
Do next week: TTFV dashboard first slice; finish AE JD (not during onsite).
Waiting on: Maya / churn list / nudge Wed night after you are home.
Someday: pricing experiment (one Linear ticket, no work this week).
Delete: none. Dentist: errand block Friday 9:00, 20 min of calls, not a work item.

3. Three priorities
P1. Leave First Prairie with a written TTFV finding (done-when: one page in Linear). Next action: 8 bullets on the plane Monday. Block: Tue 8:00-8:45 hotel. Say no: extra internal Slack during onsite.
P2. Board packet Friday 3pm (done-when: sent). Next action: outline Thursday 9:00. Block: Thu 9:00-11:30. Say no: new meetings Thursday morning.
P3. AE JD v1 to recruiter (done-when: in the hiring channel). Next action: 25 min Friday 11:00. Say no: expanding it into a full hiring plan.

4. Next-week plan
Mon: all-hands 10-11. Deep work 11:30-1:00 on TTFV bullets. Travel 3pm. No new meetings after 1:30.
Tue-Wed onsite: meetings are the work. One 45-min capture block each evening. Do not pretend these are deep-work days. Over capacity if you add homework; cut the pricing idea.
Thu: recovery is not a full day off, but 7pm birthday is fixed. Packet 9:00-11:30 and 1:00-2:30. Groceries 5:30. Dinner 7:00. Phone down after.
Fri: dentist calls 9:00. Packet polish 9:30-2:30, send 3:00. AE JD 11:00 only if packet is green. Shutdown 4:00.

8 deep-work hours: Mon 1.5, Thu 4, Fri 2.5. Onsite evenings are capture, not creation.

5. Waiting-on
Maya, churn list, nudge Wed 9:30pm: "Back from Prairie. Can I have the churn list Thursday morning for the packet?"

6. Will not track
Slack response time. Steps. Inbox zero as a score. Feature-count of guided setup.

7. 30-minute run sheet
0-5 calendar. 5-12 wins. 12-20 sort loops. 20-26 three priorities. 26-30 waiting-on + shutdown.

8. Shutdown
Week closed. Onsite is the work. Packet Thursday. Nothing else is a surprise.

Reviews (0)

Please login to leave a review.
Loading reviews...