Menu

Individual skill

shutdown-ritual

0upvotes

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.

plugins/pm-cowork/skills/shutdown-ritual/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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](../deep-work-blocking/SKILL.md) 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](../weekly-review-ritual/SKILL.md)'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:
Back to top