Claude Sonnet 5 (also works well with GPT-5.4 and Gemini 2.5 Pro — any model with strong structured-reasoning ability handles this prompt)It's Monday morning and you're staring at 14 unsorted items across your inbox, task manager, and sticky notes — three of them need deep focus, five are quick admin, four are messages you need to reply to, and two are calls. You also have three fixed meetings scattered between 10am and 3pm. Instead of tackling tasks in the order they arrived (which means bouncing between deep thinking and shallow replies all day), you want one realistic plan before you open your first tab.productivity

کاهنده تغییر زمینه: تبدیل یک لیست وظایف آشفته به یک برنامه روزانه دسته‌بندی‌شده

اشتراک‌گذاری:
کاهنده تغییر زمینه: تبدیل یک لیست وظایف آشفته به یک برنامه روزانه دسته‌بندی‌شده

Why this prompt matters

Research on workplace interruptions (Gloria Mark, UC Irvine) found it takes an average of 23 minutes to fully regain focus after a context switch. Someone who alternates between deep work and shallow admin four or five times in a single day — a completely normal pattern for anyone managing their own unsorted task list — can lose over an hour and a half of effective focus to switching costs alone, on top of the decision fatigue of constantly re-deciding what to do next. A batched plan front-loads that decision once, in the morning, instead of dozens of times throughout the day.

What we use it for

It's Monday morning and you're staring at 14 unsorted items across your inbox, task manager, and sticky notes — three of them need deep focus, five are quick admin, four are messages you need to reply to, and two are calls. You also have three fixed meetings scattered between 10am and 3pm. Instead of tackling tasks in the order they arrived (which means bouncing between deep thinking and shallow replies all day), you want one realistic plan before you open your first tab.

Prompt

Act as a productivity systems consultant who specializes in cognitive-load-aware scheduling for knowledge workers.

Context:
- My energy/focus pattern: [YOUR ENERGY PATTERN — e.g. "sharpest 9-11am, foggy after lunch until 2pm, second wind 4-6pm"]
- My fixed commitments today: [LIST YOUR MEETINGS/CALLS WITH TIMES]
- My raw, unsorted task list: [PASTE YOUR TASK LIST HERE — one per line, don't pre-sort them]

Task:
Group these tasks into batches that share the same cognitive mode (deep creative/analytical work, shallow admin, communication/social, reactive/inbox). Assign each batch to a time-of-day slot that matches my stated energy pattern, working around my fixed commitments. Minimize the number of times I switch between cognitive modes across the day.

Constraints:
- Create no more than 4 batches total.
- Every batch must include a one-sentence rationale explaining why those tasks belong together.
- Do not schedule deep/analytical work immediately after a meeting or right before a fixed commitment — treat those transition slots as shallow-work buffer zones.
- If a task doesn't fit cleanly into any batch, flag it explicitly rather than forcing it in.

Output format:
A table with columns: Time Block | Batch Name | Tasks | Rationale.
Follow the table with a short "Watch out for" section (2-3 bullets) flagging any risky transitions or tasks that were hard to place.

Result

Time BlockBatch NameTasksRationale
9:00–10:00amDeep Work: Q3 RoadmapDraft Q3 feature prioritization doc; review competitor pricing analysisBoth require uninterrupted analytical thinking and benefit from your sharpest focus window before the 10am meeting.
10:00–11:30am[Fixed] Standup + Design ReviewFixed commitments — treated as a hard boundary.
11:30am–12:30pmShallow Admin BufferApprove 3 expense reports; update project tracker; clear calendar invitesPlaced right after meetings since you're already in a reactive, lower-focus mode — no benefit lost by doing shallow work here.
1:30–2:00pm[Fixed] Client CallFixed commitment.
2:00–3:00pmReactive/CommunicationReply to 4 pending Slack threads; respond to legal's contract question; send follow-up to client from the callGrouped because your stated post-lunch fog makes this the wrong window for deep work, but you're already primed for conversational mode right after the call.
4:00–5:30pmDeep Work: Second WindowFinish competitor pricing analysis (carryover); outline next sprint's technical specYour stated second wind (4-6pm) is the only other slot with enough uninterrupted runway for analytical work.

Watch out for:

  • The 12:30–1:30pm slot is unaccounted for — if that's your lunch break, good. If not, treat it as a shallow-work overflow buffer, not a place to start anything deep.
  • "Review competitor pricing analysis" spans two batches (morning start, afternoon finish) — this is intentional since it's genuinely a 90-minute task, but confirm you're comfortable resuming analytical work mid-task rather than finishing it in one sitting.
  • You listed "brainstorm Q4 offsite ideas" as a task, but it didn't fit any batch cleanly — it's creative-generative rather than analytical or administrative. Consider giving it its own 20-minute slot rather than folding it into deep work, since forcing it alongside roadmap work may dilute both.

مورد استفاده: صبح دوشنبه است و شما به ۱۴ مورد طبقه‌بندی‌نشده در صندوق ورودی، مدیر وظایف و یادداشت‌های چسبان خود نگاه می‌کنید — سه تای آنها نیاز به تمرکز عمیق دارند، پنج تای آنها کارهای اداری سریع هستند، چهار تای آنها پیام‌هایی هستند که باید پاسخ دهید، و دو تای آنها تماس‌های تلفنی هستند. همچنین سه جلسه ثابت دارید که بین ساعت ۱۰ صبح تا ۳ بعدازظهر پراکنده شده‌اند. به جای انجام کارها به ترتیب ورود (که به معنای پرش بین تفکر عمیق و پاسخ‌های سطحی در طول روز است)، شما قبل از باز کردن اولین تب، یک برنامه واقع‌گرا می‌خواهید.

چرا اهمیت دارد: تحقیقات درباره وقفه‌های کاری (گلوریا مارک، دانشگاه کالیفرنیا، ارواین) نشان داده است که پس از تغییر زمینه، به طور متوسط ۲۳ دقیقه زمان لازم است تا تمرکز به طور کامل بازگردد. فردی که بین کار عمیق و کارهای اداری سطحی چهار یا پنج بار در یک روز جابجا می‌شود — الگویی کاملاً معمول برای هر کسی که فهرست وظایف نامرتب خود را مدیریت می‌کند — می‌تواند بیش از یک ساعت و نیم از تمرکز مؤثر خود را تنها به خاطر هزینه‌های جابجایی از دست بدهد، علاوه بر خستگی تصمیم‌گیری ناشی از بازبینی مداوم اینکه چه کاری باید انجام دهد. یک برنامه دسته‌بندی‌شده این تصمیم را یک بار، در صبح، جلو می‌اندازد، به جای ده‌ها بار در طول روز.

این پرامپت از ساختار Role + Context + Task + Constraints + Output Format استفاده می‌کند. انتخاب طراحی کلیدی این است که مدل را مجبور می‌کند جلسات را به عنوان مرزهای سخت در نظر بگیرد و وظایفی را که به‌طور تمیز جای نمی‌گیرند به‌طور صریح مشخص کند — پرامپتی که به‌طور خاموش هر وظیفه را در یک دسته منظم قرار دهد، دقیقاً نقاط اصطکاکی (مانند وظیفه‌ای که در دو دسته قرار می‌گیرد، یا وظیفه خلاقانه‌ای که نباید با کار تحلیلی مخلوط شود) را که واقعاً باعث از مسیر خارج شدن یک روز می‌شوند، پنهان می‌کند.

prompt-engineeringproductivityworkflowtime-managementfocus
اشتراک‌گذاری: