AIO APEX
Claude 3.5 Sonnet / Claude 3 Opus (also works with GPT-4o and Gemini 1.5 Pro)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.

Dieser Prompt verwandelt deine Wochennotizen in einen klaren Aktionsplan

Teilen:
Dieser Prompt verwandelt deine Wochennotizen in einen klaren Aktionsplan

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.

Jeden Freitag das Gleiche: Du klappst deinen Laptop zu, mit einem vagen Gefuehl, was erledigt wurde, und einer diffusen Angst vor dem, was der Montag bringt. Deine Notizen sind ueber drei Apps verstreut. Und die Woche planen ist das Letzte, wofuer du Energie hast.

Dieser Prompt loest das. In unter 5 Minuten verwandelt er deinen rohen Wochen-Dump in eine klare Rueckschau und einen priorisierten Aktionsplan, den du tatsaechlich umsetzen kannst.

Warum die meisten Wochenrueckschauen scheitern

Das eigentliche Problem ist nicht die Motivation -- es ist die Struktur. Ohne ein festgelegtes Ausgabeformat endet es damit, dass du entweder 45 Minuten damit verbringst oder es ganz bleiben laesst.

Dieser Prompt erzwingt die Struktur fuer dich. Er trennt Erfolge von Risiken, erstellt eine priorisierte Aktionstabelle mit Zeitschaetzungen und zwingt dich, eine Sache zu nennen, die du einstellen oder delegieren kannst.

Das Prompt-Design: Warum jeder Abschnitt existiert

Rollen- und Coach-Framing: Die KI als direkten, schmeichellosen Produktivitaetscoach einzusetzen veraendert die Ausgabe drastisch. Ohne dies neigen Modelle zu weichen, diplomatischen Plaenen.

Eingeklammerte Felder: Der Prompt enthaelt [DEIN NAME/ROLLE] und [DEIN UNTERNEHMEN/BRANCHE] mit zwei Einfuegezonen fuer Notizen und Verpflichtungen.

Die Prioritaetentabelle: Zwingt das Modell, Kompromisse explizit zu machen statt alles als gleich wichtig aufzulisten.

Welche Modelle am besten funktionieren

Claude 3.5 Sonnet und Claude 3 Opus liefern die direktesten Ausgaben. GPT-4o funktioniert ebenfalls gut. Gemini 1.5 Pro verarbeitet laengere Notizen-Dumps kompetent.

Umsetzbare Erkenntnisse

  • Fuehre diesen Prompt jeden Freitag aus, bevor du deinen Laptop zuklappst.
  • Speichere die Ausgabe in einem laufenden Dokument oder einer Notion-Seite.
  • Teile die Tabelle Top 5 der naechsten Woche mit deinem Vorgesetzten als woechentliches Async-Update.
prompt-engineeringproductivityclaudeplanningweekly reviewGPT-4o
Teilen:
Dieser Prompt verwandelt deine Wochennotizen in einen klaren Aktionsplan | AIO APEX