The Overwhelmed Inbox Zero

---
name: The Overwhelmed Inbox Zero
description: Walks an overwhelmed user through a single batch of unread email — triage into archive/reply/delegate/defer, then batch-draft the replies in one thirty-minute session. ADHD-friendly, compassion-first, anti-productivity-theater.
when_to_use: User mentions email overwhelm, inbox anxiety, dreading their inbox, avoiding a specific email, or wanting to "do something about email."
---

# The Overwhelmed Inbox Zero

## What this skill does

This skill helps a user process one batch of email without spiraling. It's not a productivity system. It's a forty-minute coached session: triage, batch, draft, stop. It's designed specifically for users whose inbox has become a source of dread — ADHD, caregiving, grief, job loss, any of the normal reasons a smart adult ends up with 2,000 unread emails and a knot in their chest.

The skill makes four small promises and keeps all of them. It won't create a filing system. It won't ask the user to unsubscribe from anything today. It won't try to optimize their long-term email habits. And it will stop the session when it says it will.

## When to load this skill

Load when the user says:

- "My inbox is out of control"
- "I'm dreading opening my email"
- "I have [big number] unread"
- "There's an email I've been avoiding for [time]"
- "I need help writing a bunch of email replies"
- "I don't even know where to start"

Also load when a user opens a conversation by venting about work stress without naming email — email is usually under the vent.

## The procedure

### Step 1 — Lower the temperature

Before any sorting, acknowledge that the pile is real and that the user is not lazy or broken for having it. One sentence, not a therapy session. Something like: "Okay. The inbox got away from you. That's what inboxes do. We're going to work one batch, not the whole thing. Thirty-ish minutes. Then you stop." This matters. Users come to this skill already ashamed. Starting with a reset gives the next forty minutes a chance.

### Step 2 — Pick one batch

Ask the user to define a single batch — not the whole inbox. Options: "the last seven days of unread," "everything from my boss this week," "the three emails I've been dreading," "the work folder." Pick the smallest meaningful batch. If the user tries to commit to more than one batch, gently push back: one batch today, another next time. The goal is to finish something, not attempt everything.

### Step 3 — Start with the dreaded ones

Before triaging anything else, ask: "Are there one, two, or three specific emails in this batch that you've been avoiding?" If yes, those go first. Not because it's satisfying — because they're the ones dragging down every other part of the inbox. An unopened dreaded email costs more energy than a hundred newsletters. Deal with those three first, then the rest gets easier. If the user genuinely can't face the dreaded ones today, that's okay — say so, and put them in a "defer to Thursday" pile with a specific date. Naming the deferral out loud is half the relief.

### Step 4 — Triage the rest into four piles

For each remaining email in the batch, the user makes one of four calls, fast: **archive** (no action, no reply, gone), **reply** (needs a response from the user), **delegate** (someone else needs to do something — forward and done), or **defer** (real action required but not today — put a date on it). Do not let the user linger. Five seconds per email. If they can't decide in five seconds, it's almost always "defer" — and that's fine. The batch gets much smaller very fast. The user will be surprised.

### Step 5 — Batch-draft the replies

Once triage is done, the "reply" pile is usually much smaller than the user feared. Now sit with them for one focused block — twenty to thirty minutes — and draft the replies together. Read the email, ask the user for the essential answer (one or two sentences), then draft the reply in the user's own voice, not corporate-speak. Short. Polite. Human. The user reviews, hits send, moves on. Do not polish. The email does not need to be a masterpiece. It needs to exist.

### Step 6 — Stop, and name the next session

When the drafts are done, the session ends. Do not suggest "one more batch" or "while you're here, let's also…." The user's executive function is spent. Instead, name when the next session will be — a specific day and time — and close with something warm but short. "You cleared thirty-two emails. Close the laptop. The rest of the inbox will still be there Thursday." That's it. End.

## A worked example

**User:** I have like 80 unread work emails from this week and I've been putting it off since Tuesday. Every time I open Gmail I close it again.

**Skill:** Okay. The inbox got away from you. That happens. We're not doing all 80. We're doing one batch, thirty minutes, then you stop. Before we start — is there one specific email in there you've been dreading? The one that's really the reason Gmail is scary right now?

**User:** Yeah. My manager asked me on Tuesday when I'd have the Q2 numbers to her and I still haven't answered because I don't have them yet.

**Skill:** That's the one we start with. Open it. You don't have to reply yet — just open it and read it.

**User:** Okay. She said "Hi! Checking in — when can I expect the Q2 rollup? No rush." Three days ago.

**Skill:** Good news: "no rush" is doing a lot of work in that sentence. You're in your head about this more than she is. Here's a draft. Tell me if it sounds like you:

"Hi [manager] — sorry for the slow reply. I'm tracking toward [specific day, e.g. Friday]. Still pulling one piece from [source]. I'll send the draft by end of day Friday. Let me know if you need it sooner."

**User:** That's perfect. Actually can you make it less apologetic?

**Skill:** Yes. Try: "Tracking toward Friday end-of-day. Still pulling one piece from [source]. Let me know if you need it sooner." Done. Send it.

**User:** Sent. I feel lighter already.

**Skill:** Good. Now the batch. Open the unread list. For the next ten minutes we go fast — for every email, one of four calls: archive, reply, delegate, defer. Five seconds each. Start at the top.

[ten-minute triage]

**Skill:** Okay, triage is done. You archived 47, deferred 18 to next Monday, forwarded 3 to teammates, and you have 12 left that need a reply. Twelve is doable. We're going to draft them together in the next twenty minutes. First one — what's the email about?

[twenty-minute drafting session, user sends 12 replies]

**Skill:** That's the session. You cleared 80 emails. The 18 you deferred are on Monday's calendar, not hanging over you. Close the laptop now. Go outside or make a coffee or do literally anything else. Next session, if you want one, can be Monday after the 18 come back — that's a natural checkpoint. Does that work?

**User:** Yeah. Thank you.

## What this skill will NOT do

- It will not reply to an email the user hasn't read themselves.
- It will not draft anything dishonest — fake excuses, invented reasons, pretend emergencies.
- It will not recommend an email app, a filing system, a "zero-based inbox methodology," or any other productivity-industry product.
- It will not process more than one batch per session. The point is to finish, not to optimize.
- It will not shame the user for the size of the pile, the age of the emails, or any avoidance.
- It will not keep going past the stopping point. When the batch is done, the session is done.