Email yourself a Daily Loose Ends list each morning

Samuel Appentsen (@champagnekofi) describes a Claude Code routine that emails one "Daily Loose Ends" packet every morning. It pulls together emails that need a reply, Slack threads that need a response, decisions waiting on them, and work projects that are halfway done. The author says they skim it in five minutes. The claim is self-reported. No full prompt was published. We have not run it.

What it replaces#

Before: opening email, Slack, the calendar, and scattered project sessions to rebuild what still needs you. After: one morning email with the top three for the day, today's calendar, and every reply owed with how many days it has been waiting. The author ticks items off, snoozes some, and drafts replies straight from that list.

They say it is "far easier than any task manager, because I don't have to put anything into it. It finds the loose ends for me."

How it works#

The post names the stack (Claude Code, email, Slack, and every Claude Code session they have running) and the output shape, not a copy-paste skill file. Adapt with a starter like the one below, then tighten it against your own folders and labels.

1. Connect Claude Code to the email account it should read and send from, plus Slack read access, and point it at the project folders or sessions that hold half-done work.
2. Define what counts as a loose end: unreplied mail older than N days, Slack threads where you were asked a question, open decisions assigned to you, and projects with unfinished local changes or open todos.
3. Shape the email: top three for today, today's calendar, then the reply queue with age in days. Keep send disabled except for the one Loose Ends email to yourself.
4. Schedule it every morning before you open Slack. On the first week, compare the email to what you would have found by hand and trim false positives.

Starter shape (not the author's verbatim prompt; shaped from their description):

Every morning, build my Daily Loose Ends email and send it only to me.
Sources: my email, Slack, today's calendar, and my active Claude Code
sessions or project folders.
Include: (1) my top three priorities for today, (2) today's calendar,
(3) every reply I owe in email or Slack with how many days it has waited,
(4) projects that look halfway done.
Do not send any reply to other people. Do not close threads. Leave
anything ambiguous in an Exceptions section for me.

What you need connected#

Claude Code with a morning schedule, an email account the routine can read and mail from, Slack read access, and whatever local sessions or folders hold half-finished work. The author says it is "connected to my email, Slack and every Claude Code session I've got running."

Good to know#

• This is a find-and-surface job. The author still ticks, snoozes, and drafts. The routine does not claim to clear the queue on its own.
• Privacy matters if the same pattern is rolled out at a company. The author argues every employee should get a private, AI-first version of this, because "big organisations are full of scraps" in threads and inboxes. Keep each person's packet private to them.
• No minutes-before figure was published, only the five-minute skim. Treat the time claim as self-reported.
• We did not reproduce the routine on this box.

Same idea in Grok Bot#

Grok Bot can run a morning scheduled routine that reads Gmail and Slack and emails you a numbered Loose Ends page, drafts only. Save the method as a skill. Put outbound replies behind approval. For half-done local projects, only claim what your Bot can see (computers, repos, or notes you connected). Do not invent a Slack or mail connector you do not have.

Sources#

• champagnekofi on X, Oct 12, 2026 (6:16 PM ET)