Turn Your Weekly Notes into a Clear Action Plan with This Prompt
Why this prompt matters
Without a structured weekly review, most professionals repeat the same mistakes week over week -- dropping important-but-not-urgent work, failing to flag risks early, and spending Monday morning reconstructing what needs to happen instead of executing. Research shows that pre-planned weekly priorities cut decision fatigue significantly and reduce dropped commitments. This prompt forces that discipline in under 5 minutes.
What we use it for
You have just finished Friday afternoon with a stack of notes, a half-done to-do list, and a vague sense of what next week holds. You have 15 minutes before you close the laptop. This prompt turns that raw material into a crisp, honest weekly review and a prioritized action list -- so you start Monday with clarity instead of catching up.
Prompt
Act as a professional productivity coach and strategic planner with experience working with senior professionals across tech, finance, and consulting. Context: You are helping [YOUR NAME/ROLE] at [YOUR COMPANY OR INDUSTRY] conduct a thorough end-of-week review and build a focused plan for the week ahead. Task: Using the notes I provide below, do the following in order: 1. Write a concise weekly review (3-5 sentences) that honestly captures what was accomplished, what was not, and why. 2. Identify 2-3 key wins worth recognizing. 3. Flag any risks, blockers, or commitments at risk of slipping. 4. Generate a prioritized list of the top 5 actions for next week, ordered by impact. For each, include: the action, why it matters, and how long it should take. 5. Identify one thing to STOP doing or delegate this week. Constraints: - Be direct and honest -- skip the compliments, skip the hedging. - If the notes are vague, ask a clarifying question rather than guess. - Keep each section tight: no bullet point should exceed 2 lines. - Do not repeat information across sections. Output Format: ## Weekly Review [3-5 sentences] ## Key Wins - [win 1] - [win 2] - [win 3 if applicable] ## Risk Flags - [risk/blocker 1] - [risk/blocker 2 if applicable] ## Next Week Top 5 Actions | Priority | Action | Why It Matters | Est. Time | |----------|--------|----------------|-----------| | 1 | | | | | 2 | | | | | 3 | | | | | 4 | | | | | 5 | | | | ## One Thing to Stop or Delegate [1-2 sentences] --- My notes for this week: [PASTE YOUR WEEK NOTES, DONE ITEMS, CALENDAR, BLOCKERS HERE] Next week known commitments: [PASTE MEETINGS, DEADLINES, OR GOALS ALREADY SCHEDULED]
Result
## Weekly Review
This was a productive week on the delivery side -- the API integration shipped on schedule and the design review for the mobile dashboard wrapped earlier than expected. However, stakeholder alignment on Q3 OKRs slipped: the planned Friday sync did not happen, and two engineering leads are still misaligned on scope. Documentation for the new onboarding flow was not started despite being on last week plan.
## Key Wins
- API integration shipped on time with zero critical bugs in initial testing
- Mobile dashboard design review completed 2 days early, freeing up capacity
- Successfully unblocked the data team by clarifying the schema change in Tuesday async thread
## Risk Flags
- Q3 OKR alignment meeting not yet rescheduled -- two engineering leads have conflicting scope assumptions that will surface in sprint planning Thursday
- Onboarding flow documentation 0% complete; external contractor starts in 9 days with no docs ready
## Next Week Top 5 Actions
| Priority | Action | Why It Matters | Est. Time |
|----------|--------|----------------|-----------|
| 1 | Reschedule Q3 OKR alignment; send pre-read doc by Tuesday | Unresolved scope misalignment will disrupt sprint planning Thursday | 2 hrs |
| 2 | Draft onboarding flow documentation outline, assign sections to team | Contractor starts in 9 days; zero docs = blocked onboarding | 1.5 hrs |
| 3 | Kick off mobile dashboard usability test recruitment | 3-week lead time for participants; delay now = delay in release | 45 min |
| 4 | Review API integration test results and write post-mortem | Shipping without retrospective means repeating the same friction points next sprint | 1 hr |
| 5 | Set up weekly 15-min async status update for stakeholders | Ad-hoc Slack pings fragmented 6+ hours this week -- structured update reduces interruptions | 30 min |
## One Thing to Stop or Delegate
Stop manually compiling the weekly metrics digest -- hand it off to the ops coordinator using the existing dashboard export. This consumes 90 minutes per week with zero strategic value.
<p>Every Friday, the same thing happens: you close your laptop with a rough sense of what got done and a vague anxiety about what Monday holds. Your notes are scattered across three apps. Your to-do list is half-accurate. And planning the week is the last thing you have energy for.</p><p>This prompt solves that. In under 5 minutes, it transforms your raw weekly dump -- notes, done items, calendar fragments, blockers -- into a clear review and a prioritized action plan you can actually follow.</p><h2>Why Most Weekly Reviews Fail</h2><p>The common problem is not motivation -- it is structure. Without a defined output format, doing a weekly review means staring at your notes and thinking in circles. You end up either spending 45 minutes on it or skipping it entirely. Both outcomes are bad.</p><p>This prompt enforces the structure for you. It separates wins from risks, generates a prioritized action table with time estimates, and forces you to name one thing to stop or delegate -- the step most people skip and most regret skipping.</p><h2>The Prompt Design: Why Each Section Exists</h2><p><strong>Role + Coach framing:</strong> Setting the AI as a direct, no-flattery productivity coach changes the output dramatically. Without this, models tend to validate everything you did and produce soft, diplomatic plans. The framing pushes it toward honest assessment.</p><p><strong>[Bracketed fields]:</strong> The prompt includes [YOUR NAME/ROLE], [YOUR COMPANY OR INDUSTRY], and two paste zones for weekly notes and next week commitments. These are essential -- without context, the AI generates generic advice. With them, it produces specific, prioritized output.</p><p><strong>The priority table:</strong> Asking for a table with Action, Why It Matters, and Estimated Time forces the model to make tradeoffs explicit rather than listing everything as equally important. The Why It Matters column is where the real thinking happens -- it surfaces assumptions you did not know you were making.</p><p><strong>One Thing to Stop or Delegate:</strong> This is the most underrated section. Every professional has tasks they have been doing out of habit that a tool, system, or colleague could handle. Naming it weekly makes the pattern visible.</p><h2>Which Models Work Best</h2><p>Claude 3.5 Sonnet and Claude 3 Opus deliver the most direct, well-structured output with this prompt. GPT-4o works well too -- add Be direct; avoid flattery to the constraints section if the output feels too diplomatic. Gemini 1.5 Pro handles it capably for longer note dumps.</p><h2>Actionable Takeaways</h2><ul><li>Run this prompt every Friday before you close your laptop -- even 10 minutes of notes is enough input.</li><li>Save the output to a running doc or Notion page. Patterns emerge after 4-6 weeks.</li><li>Share the Next Week Top 5 table with your manager or team lead as your weekly async update -- it takes 30 seconds to paste and replaces a 15-minute status meeting.</li><li>The One Thing to Stop or Delegate section is the highest-ROI habit to track over time.</li></ul>