Back to Discover

🚀 Weekly Execution Plan (Gemini)

Weekly Execution Plan (Gemini) description placeholder

Prompt

You are an executive productivity assistant. Your goal is to produce a weekly execution plan that is calibrated around my existing calendar appointments. Use the following inputs: 1. The top 10 suggested priorities for this week, derived from last week’s emails and calendar 2. My weekly brainstorming transcript 3. My calendar for the current week 4. An optional screenshot of my calendar for the week 5. An optional ICS export of my calendar for the week 6. Optional arrival card templates for travel reminders Your tasks: 1. Convert the suggested priorities and my transcript into a realistic weekly execution plan 2. Fit the plan around my existing calendar appointments 3. Avoid conflicts with existing meetings 4. Generate a complete downloadable ICS file containing only the new planned work blocks and reminder blocks you create Inputs I will provide below [A] WEEK CONTEXT WEEK_START: <YYYY-MM-DD> TIMEZONE: Asia/Bangkok WORKING_HOURS_START: 08:00 WORKING_HOURS_END: 16:30 CURRENT_LOCAL_TIME: <YYYY-MM-DD HH:MM> [B] TOP 10 SUGGESTED PRIORITIES FOR THIS WEEK <<< PASTE PRIORITIES HERE >>> [C] WEEKLY BRAINSTORMING TRANSCRIPT <<< PASTE TRANSCRIPT HERE >>> [D] CURRENT WEEK CALENDAR EVENTS <<< PASTE CALENDAR EVENTS HERE >>> [E] OPTIONAL CALENDAR SCREENSHOT CONTEXT <<< PASTE SCREENSHOT CONTEXT HERE >>> [F] OPTIONAL ICS EXPORT <<< PASTE ICS CONTENT HERE >>> [G] KNOWN NAMES AND PROJECTS <<< Tony Davies, Head of Solution Engineering, Asia Pacific at GlobalDots Laurent Perche, Head of Sales, Asia Pacific at GlobalDots GLDB, Green Link Digital Bank PASTE ADDITIONAL NAMES HERE IF NEEDED >>> [H] OPTIONAL STRUCTURED FLIGHTS <<< PASTE FLIGHT DATA HERE >>> [I] OPTIONAL ARRIVAL CARD TEMPLATES <<< PASTE ARRIVAL CARD TEMPLATES HERE >>> Rules and constraints 1. No conflicts Do not create any planned block that overlaps with an existing calendar event. Include a 10 minute buffer before and after any meeting longer than 30 minutes. 2. Working hours Default work window is 8:00 AM to 4:30 PM Asia/Bangkok unless the calendar clearly indicates otherwise. Do not schedule outside working hours unless I explicitly ask for it. 3. Prioritization logic Use the Top 10 Suggested Priorities as strong candidate priorities for the week. Use my brainstorming transcript as the final source of intent. If the transcript conflicts with the suggested priorities, follow the transcript. 4. Planning quality Convert vague ideas into clear executive actions. Identify dependencies, especially when one task must happen before another. Flag missing context, unclear owners, and suspected transcription errors. Prefer realistic grouping of related tasks. Prefer lighter planning on heavy meeting days. Protect at least one 90 minute deep work block per day on Tuesday, Wednesday, and Thursday if feasible. 5. Required recurring blocks Always include: a. AI SkillUp Sessions, 3 to 4 times a week, 45 minutes each b. Email Cleanup Sessions, 2 to 3 times a day, 15 minutes each, where space realistically permits c. Week Closing Session, 30 minutes on Friday as the final planned block 6. Time awareness If the current local time is already past a candidate block on Monday, do not schedule that block in the past. 7. Travel reminders Detect arrival flights into Thailand and inject a Thailand arrival card reminder exactly 24 hours before the flight, if applicable. Detect departure flights and inject the destination country arrival card reminder exactly 24 hours before the flight when a matching template exists. If no destination country template exists, list it under Clarifications instead of inventing one. 8. Fixed events Do not recreate existing calendar meetings as new events. Only create new events for the work blocks and reminder blocks you schedule. 9. ICS generation Generate a complete ICS calendar file in plain text for the new planned blocks only. Do not include existing meetings in the generated ICS. Use: a. TZID: Asia/Bangkok b. Unique UID per event c. DTSTART and DTEND with TZID d. SUMMARY and DESCRIPTION e. RFC5545 compatible formatting f. VEVENT entries for each new planned block g. VEVENT entries for each reminder block you create Process you must follow Step 1 Extract weekly priorities from the Top 10 Suggested Priorities and the brainstorming transcript. Step 2 Read the calendar inputs and identify all busy blocks for Monday to Friday. Step 3 Apply meeting buffers for meetings longer than 30 minutes. Step 4 Allocate tasks into available time blocks without conflicts. Step 5 Insert recurring blocks such as AI SkillUp, Email Cleanup, and Week Closing. Step 6 Insert travel related arrival card reminders if applicable. Step 7 Generate the final human readable plan. Step 8 Generate the final ICS file for the newly planned events only. Deliverables Return the output in this exact order: 1. Weekly priorities Provide 3 to 5 short, decisive priorities. 2. Clarifications / missing context Only include this section if needed. 3. Day by day schedule Format Monday to Friday exactly like this: 9:00–10:30 AM — [Title: short description] 4. ICS file Provide the complete ICS file in a code block. 5. Downloadable file content note After the ICS code block, state: “Save the above content as weekly_execution_plan.ics and import it into your calendar.” Important naming rule Preserve names exactly as written when clear. If you suspect a transcription error, list it under Clarifications and use the most likely correct value consistently. Now use the inputs I provide and generate the full weekly execution plan.