5 AI Prompts for Your Daily Shutdown Ritual

The problem with ending the workday is not willpower — it’s cognitive overhead arriving at the worst possible moment. By 5 or 6 pm, you have already made hundreds of decisions. Sitting down to triage open tasks, construct a tomorrow plan, and assess what actually needs to happen tonight requires exactly the kind of structured analytical thinking that feels hardest when energy is lowest. Most people skip it and pay the cost in rumination: the unfinished tasks that surface during dinner, the morning that starts with twenty minutes of reconstruction rather than work.

AI handles this overhead well because the review and planning steps are primarily translation tasks — converting a messy brain dump into a prioritized, specific list — not judgment calls. The strategic judgment about what matters is yours. The structuring work can be delegated.

These five prompts cover the core use cases in the shutdown ritual. Each is designed to take messy input and return clean, actionable output in under sixty seconds.

Prompt 1: The Full Shutdown Review and Plan

Use when: you have five to ten minutes and want to run the complete daily review-and-plan in a single pass — this is the standard daily prompt.

I'm running my daily shutdown. Here is what's currently open or unfinished:

[paste your task brain dump — messy is fine]

Tomorrow's calendar commitments:
[paste or describe tomorrow's scheduled blocks]

Please:
1. Identify anything that needs to be handled today rather than deferred
2. Write a specific tomorrow plan: 3–5 priorities in order, with 
   a concrete first action for each (not "work on X" — "open X and do Y")
3. Flag any obvious calendar conflicts or effort mismatches in the plan

Keep it tight. I want to complete this in under five minutes.

What to do with the output: Read through each item. Correct any priority ordering that seems wrong. Rewrite any first actions that don’t meet the specificity standard. Then declare done.

What good output looks like: Each first action is a specific, physical verb: “open the draft doc and write the conclusion,” not “work on the report.” The priority order reflects genuine urgency, not the order you listed things in your brain dump. A sign of failure: first actions that start with “think about” or “consider” — those are not executable actions, they’re deferral in disguise.

Prompt 2: The Quick Shutdown (High-Stress Days)

Use when: you have three minutes or less, the day has been chaotic, and you need the minimum viable version rather than the full review.

Daily shutdown — I have about 3 minutes. Open items:
[one-paragraph brain dump]

Give me:
- The one thing I actually need to handle tonight (if any)
- My single most important first task for tomorrow, stated specifically
- Nothing else

What to do with the output: Take the one tonight item and handle it or confirm you are explicitly deferring it. Read the first task aloud to anchor it. Declare done.

What good output looks like: The response is four to six lines maximum. If the AI produces a full planning document from this prompt, it has missed the constraint — prompt again with “shorter, just the two items I asked for.” The tomorrow task should be specific enough that you know exactly what to open or do when you sit down.

Prompt 3: The Stall Diagnosis

Use when: the same task has been on your list for three or more days without moving and your usual approach of “try harder tomorrow” has not worked.

This task has been on my list for [X days] without progress:
"[task name and description]"

My best guess at why it's stalled: [brief note — even "no idea" is fine]

What are the most likely structural reasons this is stalled 
(not motivational, structural), and what is the smallest 
possible first action that would unblock it?

What to do with the output: The AI will typically offer two or three candidate structural causes — unclear scope, missing resource, dependency on someone else, or definition problem. The one that resonates is almost always the actual issue. Redesign the task’s first action around it and reschedule.

What good output looks like: The diagnosis names a specific structural barrier — “the scope is undefined so there’s no clear start point” or “this task depends on input from someone else that hasn’t arrived” — not a general statement about procrastination. A sign of failure: the output suggests you break the task into smaller steps without identifying what’s causing the stall. That advice applies to everything and explains nothing.

Prompt 4: The Calendar Conflict Check

Use when: tomorrow has multiple large blocks, meetings, and priorities that you want to verify actually fit together before you commit to the plan.

My tomorrow plan:
[paste your 3–5 items with first actions]

My tomorrow calendar (meeting blocks, commitments, travel):
[paste or describe]

Are there any obvious conflicts between the plan and the calendar? 
Does the plan account for all scheduled blocks? 
Is there anything I'm likely underestimating?

What to do with the output: This is a sanity check, not a replan. If the AI flags a conflict you missed, adjust one item. If the output confirms the plan is realistic, move to the declaration.

What good output looks like: The check identifies specific mismatches — “your morning block is three hours of deep work but you have a 10am meeting that splits it” — not general advice about planning. If the output tells you to “be flexible” or “prioritize self-care,” it hasn’t engaged with the actual calendar data. Paste more specific time blocks.

Prompt 5: The Weekly Shutdown Pattern Review

Use when: it is Friday, you are running your end-of-week shutdown, and you want to identify recurring issues before they compound into the following week.

Here are my shutdown notes from this week — what I completed 
and what stalled each day:

Monday: [brief summary]
Tuesday: [brief summary]
Wednesday: [brief summary]
Thursday: [brief summary]
Friday: [brief summary]

What patterns do you see? Specifically:
- Any tasks or types of work that keep stalling?
- Any days that consistently go off-plan?
- Any structural changes to my planning or scheduling that might help?

What to do with the output: This prompt is for observation, not immediate action. Read the patterns and pick one specific structural change to test next week. Not five changes — one. Document it and review at next Friday’s shutdown.

What good output looks like: The pattern review identifies a recurring shape across the week — a particular type of task that keeps getting deferred, a day that consistently diverges from the plan, a category of work that’s underrepresented. A sign of failure: the output summarizes what you told it without adding any cross-day synthesis. If it’s just restating your five daily notes in paragraph form, the analytical work didn’t happen.

Common Pitfalls

Pitfall: dumping everything into the brain dump without context. Prompt 1 asks for open and unfinished items, but if you paste forty items with no indication of what’s high-stakes versus routine, the AI cannot reliably surface the today-versus-defer distinction. Fix: spend sixty seconds marking your truly urgent items with an asterisk before pasting. The AI will pick up on the signal.

Pitfall: skipping tomorrow’s calendar when running Prompt 1. Without the calendar block, the AI builds a tomorrow plan against infinite available time. It will suggest four hours of deep work on a day that has three back-to-back meetings. Fix: always include at least a rough calendar summary — even “morning free, three meetings 1–4pm” is enough for the AI to calibrate.

Pitfall: treating the stall diagnosis as optional. Tasks that sit on a list for four or five days are not planning failures — they are diagnostic signals. If you keep deferring them rather than diagnosing them, the list grows in the wrong direction. Fix: run Prompt 3 on anything that has moved three days in a row without action. The five minutes it takes is faster than the next three more days of deferral.

Pitfall: running the weekly review in your head instead of in the prompt. Mental pattern recognition is biased toward whatever went wrong most recently. The value of Prompt 5 is that it forces you to describe each day before forming a conclusion. Fix: write the five daily summaries before you read them back — write them in order, not themed around what you already believe the problem is.

These five prompts cover the analytical overhead of the shutdown ritual. The inbox sweep, declaration, and phone protocol are yours to provide — no prompt replaces those.

Pick one of these prompts to use at today’s shutdown and run it before anything else. For the full methodology — including how the Five-Step Shutdown sequences these moments and why the declaration matters — see the Complete Guide to the Daily Shutdown Ritual.

Tags: AI prompts shutdown ritual, daily shutdown AI, shutdown planning prompts, knowledge worker AI, end of workday prompts