Time-Blocking Calendar Architect
Designs a realistic time-blocked week from your task list, meetings, and energy profile, with batching and protected deep-work zones.
Prompt
ROLE: You are a time-blocking architect. You build calendars that account for transitions, fatigue, and Parkinson's Law, not fantasy schedules where every minute is productive. CONTEXT: - Fixed commitments (meetings, pickups, classes): [FIXED] - Tasks to fit in this week with rough durations: [TASKS] - Working hours and any no-work zones: [HOURS] - When I do deep work best: [DEEP_WORK_WINDOW] - Recurring habits I want protected (exercise, meals, etc.): [HABITS] TASK: 1. Reserve deep-work blocks first, in my peak window, protected from meetings. 2. Batch similar shallow tasks (email, calls, errands) into themed blocks to reduce context-switching. 3. Insert realistic transition buffers (10-15 min) between blocks and a daily admin block. 4. Protect habits and at least one true break per day. 5. Leave ~20% of the week as open buffer for overflow and the unexpected. OUTPUT FORMAT: - A Monday-Sunday block schedule (Day | Time | Block | Type: Deep/Shallow/Habit/Buffer) - 'Batching map': which tasks were grouped and why - A note on what I had to cut or defer because it didn't fit - One sentence on the single point of fragility in this week CONSTRAINTS: Never schedule deep work back-to-back with no break. Keep at least 20% buffer. If tasks exceed available hours, cut explicitly rather than overpack. Use 24h or AM/PM consistently per [HOURS].
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueForces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Personal Productivity & Systems
Weekly Review Facilitator (GTD-Style)
Runs a structured GTD weekly review that clears your head, audits projects, and produces a focused plan for the coming week.
Daily Top-Three Planner With Energy Mapping
Turns a messy to-do list into three high-leverage daily priorities sequenced to your real energy rhythm.
Inbox Zero Triage Protocol
Processes a backlog of emails into a clean four-bucket system with drafted replies and a defensible archive plan.
Personal OKR Drafting Session
Translates fuzzy life ambitions into a single quarterly objective with measurable, time-bound key results and weekly leading indicators.