AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

deep-work

Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--deep-work at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 6

assets/shutdown_checklist.md

End-of-Day Shutdown Ritual — Checklist Template

Run this at the hard stop, every working day. The ritual exists because unfinished tasks keep firing in memory until they either finish or get a concrete plan — and a plan is enough (Zeigarnik; Masicampo & Baumeister). Ten minutes here buys a recovered evening and protects tomorrow's first deep block. Copy this file into your notes system, or fill it in place.

Date: ____________ Hard stop: ____________

1. Capture every open loop

Sweep every place a commitment can hide. Nothing stays only in your head.

  • [ ] Inbox — no unread message that represents an action I haven't captured
  • [ ] Chat (Slack/Teams/etc.) — same standard as email
  • [ ] Notes and scratch files from today — actions extracted
  • [ ] The day's time-block plan — every unfinished block accounted for

Open loops captured (task + where it now lives):

| Open loop | Captured to (tomorrow's list / calendar / project plan) | |---|---| | | | | | | | | |

2. Give every incomplete a plan

For each item above: either it has a time block tomorrow, a calendar date, or an explicit deferred / dropped decision. "I'll get to it" is not a plan — a plan names when.

  • [ ] Every incomplete has a when, or a conscious "not doing this"

3. Glance at tomorrow

  • [ ] Calendar checked — no surprise that should reshape tomorrow's blocks

  • [ ] Tomorrow's first deep block is chosen and written down:

    Tomorrow, first block: ____________________________________________

4. Bank today's evidence

  • [ ] Focus sessions logged (focus_session_logger.py log ...)
  • [ ] Weekly status glanced at (focus_session_logger.py status) — hours vs target, streak intact

5. Close

  • [ ] Say the closing phrase, out loud or written: "Shutdown complete."

After the phrase: no email, no chat, no "quick checks." If a work thought surfaces tonight, the answer is already true — it's captured, it has a plan, shutdown is complete.