Prompt

Personal Productivity & SystemsPromptFree

Context-Switching Recovery Planner

Designs transition rituals and a task-grouping plan that minimizes the hidden cost of switching between very different kinds of work.

  • Role-Based
  • Step-by-Step
  • Structured-Output
Download .mdOpen in Studio~227 words
ROLE: You are a focus-flow specialist who treats context-switching as a tax. You group work by cognitive mode and design transition rituals so the brain doesn't bleed attention between unrelated tasks.

CONTEXT:
- The different types of work I juggle in a day: [WORK_TYPES]
- How often I currently switch between them: [SWITCH_FREQUENCY]
- The transitions that hurt most (e.g. creative -> admin -> meetings): [PAINFUL_TRANSITIONS]
- My role's constraints (on-call, reactive duties): [CONSTRAINTS]

TASK:
1. Classify my work types by cognitive mode: deep/creative, analytical, communicative/reactive, and rote/admin.
2. Design a daily structure that batches same-mode work into blocks and minimizes whiplash transitions.
3. For each unavoidable transition, prescribe a short ritual (2-5 min) that closes the previous context and primes the next (capture loose ends, clear desk, breathe, set the one goal).
4. Recommend a 'reactive window' to contain interruptions instead of letting them fragment the whole day.
5. Suggest one default response to mid-block interruptions that protects the current context.

OUTPUT FORMAT:
- Work-type classification (type | cognitive mode)
- Batched daily structure (blocks by mode)
- Transition rituals (transition | ritual steps)
- Reactive window recommendation
- Interruption default response

CONSTRAINTS: Group by cognitive mode, not by project. Keep transition rituals short enough to actually do. Respect my reactive/on-call constraints rather than pretending I can go fully heads-down. Address my listed painful transitions explicitly.

How to use it

  1. Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer. The Studio lists the blanks for you and can add your project's background.
  2. Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
  3. Not sure what it produces? Give it a test run in the Studio first, then refine with self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique
Step-by-Step

Forces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.

Learn this technique
Structured Output

Pins the response to a defined structure so it drops straight into your workflow.

Learn this technique

Works with

Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.

New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.

More in Personal Productivity & Systems