---

name: shutdown-ritual description: "End the workday on purpose — the ten-minute shutdown that closes open loops, stages tomorrow's start, and gives the brain permission to actually stop (the incomplete-task hum has an off switch, and it's written). Use when asked I can't stop thinking about work at night, build an end-of-day routine, my evenings are ruined by open loops, or how do I stop checking one more time. Produces the shutdown checklist, the tomorrow-staging step, the closing phrase, and the after-hours boundary rules."

Shutdown Ritual Skill

The workday that never ends doesn't end because it was never ended — open loops hum all evening (the unsent reply, the half-decision, the thing you might forget), and the brain, which can't tell captured from uncaptured, keeps rehearsing all of it. The shutdown is ten minutes of deliberate ending: sweep the loops into the system (written = the hum's off switch), stage tomorrow's start (the named first task — deep-work-blocking entry ritual's supplier), glance the calendar for ambushes, and close with the phrase — the verbal marker that sounds silly and works, because rituals are how brains change state.

What This Skill Produces

• The shutdown checklist — the ten-minute sequence, ordered, tuned to the user's actual systems
• The staging step — tomorrow's first task named and its materials left open (weekly-review-ritual's daily sibling)
• The closing phrase — the state-change marker, chosen by the user, used every time
• The boundary rules — the after-hours contract: what genuinely reopens work (defined narrowly), and the phone mechanics that make the contract keepable

Required Inputs

Ask for these if not provided:

• The leak pattern — what actually intrudes at 9pm: unfinished tasks? Unsent messages? Tomorrow-anxiety? Rumination on the day's friction? The checklist weights toward the real leak
• The systems — where tasks and notes live; the sweep needs destinations (task-triage-matrix intake), and head-only carriers need the capture habit installed first
• The hard stop's reality — a fixed end time, or variable? Rituals attach best to consistent triggers (the calendar block, the commute, the laptop-close)
• The after-hours pressure — does the job genuinely require evening reachability? The boundary rules negotiate reality, not fantasy (working-agreements material when it's a team norm problem)

Framework: The Ritual Rules

1. Sweep the loops, in writing: every open thing — the unsent reply (send it in two minutes or task it — email-triage-system verbs), the half-decision (task with its next step), the might-forget (captured) — the head emptied into the system. The written loop stops humming; this single step is most of the ritual's power.
2. Stage tomorrow's entry: the first task named specifically ("finish section 3," not "continue the doc"), its document left open or its materials staged — tomorrow-you starts rolling instead of choosing ([the entry ritual receives this]). The staging also answers tonight's "what about tomorrow?" hum preemptively.
3. The ambush glance: thirty seconds on tomorrow's calendar — the 8:30 meeting discovered tonight is a schedule fact; discovered at 8:25 it's a panic. Anything needing prep gets its task now.
4. Close with the phrase, every time: "shutdown complete" (or the user's variant) — spoken, mildly ridiculous, and effective for the same reason all rituals work: consistent marker, state change. The phrase means the system has everything; nothing is carried in the head; earned each time by the sweep that precedes it.
5. The boundary has mechanics, not willpower: work apps off the phone's first screen (or signed out — friction is the honest enforcement), notifications off after the phrase, and the reopen-contract defined narrowly in advance ("production down or the boss calls — everything else is tomorrow's") — because an undefined emergency channel defaults to everything (out-of-office-designer urgency logic, applied nightly). The one-more-check impulse gets its honest answer: checking is reopening; the ritual either ended the day or it didn't.

Output Format

Shutdown Ritual: [name] — [trigger: time/event], 10 min

The Checklist

[1. Loop sweep → the systems (5 min) · 2. Stage tomorrow's first task + materials (2) · 3. Calendar ambush glance (1) · 4. The phrase (spoken)]

The Staging Note (today's)

[Tomorrow starts with: (the named task) · staged: (what's left open)]

The Boundary Contract

[The narrow reopen-definition · the phone mechanics (apps moved/signed out, notifications off) · the one-more-check answer, written]

Quality Checks

• The sweep empties the head into real systems, in writing
• Tomorrow's first task is named at do-this grain and staged
• The calendar glance happened — no morning ambushes
• The phrase is chosen and used every time, earned by the sweep
• The reopen-contract is narrow, written, and the phone mechanics enforce it

Anti-Patterns

• Do not shut down by walking away — unswept loops hum all evening; the ritual is the off switch
• Do not stage vaguely — "continue working on X" restarts tomorrow with the choosing tax
• Do not leave the emergency channel undefined — undefined defaults to everything, nightly
• Do not run the ritual sometimes — inconsistent rituals don't change state; the streak is the mechanism
• Do not do one more check after the phrase — it's not a check, it's a reopening, and the brain knows

Example Trigger Phrases

• "I can't stop thinking about work at night."
• "Build an end-of-day routine."
• "My evenings are ruined by open loops."
• "How do I stop checking one more time?"