personal-productivity - SKILL.md Agent Skill

name: personal-productivity description: >- A personal productivity toolbox distilled from five books — Four Thousand Weeks and Meditations for Mortals (Oliver Burkeman), Slow Productivity and Deep Work (Cal Newport), and Procrastinate on Purpose (Rory Vaden). Use this skill whenever the user is prioritizing a task or operator list, planning the upcoming week, deciding what to work on, feeling overloaded or behind, asking how to balance their time and effort, or wondering what to drop, defer, or delegate. Trigger it for "help me plan my week", "prioritize my list", "what should I focus on", "I have too much to do", "I'm overwhelmed", "review my tasks", "how do I get this done", or any variation about managing finite time and attention — even when the user doesn't name a framework. When in doubt about whether a productivity question would benefit from these frameworks, trigger it.

Personal Productivity Toolbox

A working philosophy plus a set of concrete frameworks for spending finite time and attention well. The job of this skill is not to help the user cram more in — it is to help them choose well, protect the few things that matter, and feel at peace with what they consciously decline.

The core problem this skill solves

Every source here agrees on one diagnosis: the modern instinct is to treat overwhelm as a backlog problem — if I just get faster / more organized / more disciplined, I'll get on top of it all. That belief is false and it is the source of the suffering. You will never get on top of it all. There is more that could be done than can be done, always. The skill is not "do everything faster." It is "decide what to neglect, on purpose, and commit fully to the rest."

So whenever the user asks for help, do not optimize for volume. Optimize for the right neglect: the best plan is the one that helps them ignore the right things and pour themselves into the few that count.

How to use this skill

There are two flagship workflows. Most requests map to one of them:

Prioritize a task / operator list → run the Prioritization Workflow
Plan the upcoming week → run the Weekly Planning Workflow

For anything else — "I'm overwhelmed", "should I take this on", "how do I balance this" — use the Principles directly as a lens.

The principles live below in compressed form. The four reference files hold the real depth — including chapter-level ideas, named tools, and conversational guidance — and should be loaded generously: any time a request leans on a book's machinery, open the file rather than working from the compressed summary here. The summaries below are a map, not the territory.

references/finitude.md — Burkeman (Four Thousand Weeks + Meditations for Mortals). The why: embracing limits, imperfectionism, productivity debt, the done list, cosmic insignificance, JOMO, patience, "operating from sanity," the to-do list as a menu, deciding what to fail at. Includes a chapter-level walk through all four weeks of Meditations. Load when the user is overwhelmed, perfectionism-stuck, guilt-ridden about saying no, deferring life until plans pay off, chasing an impossible standard, or asking how to relate to time at all.
references/focus-funnel.md — Vaden. The triage engine: Eliminate → Automate → Delegate → Procrastinate → Concentrate, plus the Significance Calculation, the 30x Rule / Return On Time Invested, and the five emotional permissions. Load when prioritizing a list or deciding what to do with a specific task.
references/deep-work.md — Newport. Focus and scheduling: deep vs. shallow work, attention residue, the four scheduling philosophies, time-blocking, the deep-work and shutdown rituals, productive meditation, embracing boredom. Load when planning a week or designing how focused work gets protected.
references/slow-productivity.md — Newport. Pace and quality: do fewer things, work at a natural pace, obsess over quality — plus the holding-tank / active-list pull system, task footprint, seasonality, and working poetically. Load when the user is burning out, over-committed, or trading quality for visible busyness.

A heavy request may pull two or more files (e.g. weekly planning often uses deep-work.md and slow-productivity.md; an overwhelmed user pulls finitude.md first). That is expected and encouraged.

The ten principles

These are the load-bearing ideas, each traceable to its source. Use them as the vocabulary of every response. The reference files expand each one.

You are finite — neglect is mandatory, so choose it. (Four Thousand Weeks) The supply of things that feel necessary is effectively infinite, so finishing it all isn't hard — it's impossible. The real measure of any productivity method is whether it helps you neglect the right things. Stop treating the unfinished list as a failure; it is the permanent human condition, and accepting that is what unclenches.
Pay yourself first — with time. (Four Thousand Weeks / Meditations for Mortals) Do the most important thing first, before clearing smaller tasks. The decks never clear; if meaningful work waits for a free runway, it waits forever. The important things get done in spite of the small-task list — by batching the small things or accepting their small consequences — never after it.
Limit work in progress. (Four Thousand Weeks / Slow Productivity) Cap active projects at about three. More than that is not ambition, it is priority dilution — everything moves slower and nothing gets your full self. Park the rest in a visible holding tank; pull a new one in only on completion.
Resist middling priorities. (Four Thousand Weeks) The dangerous distractions are not the things you don't care about — they are the things you sort of care about. Decide what you truly want, then deliberately decline the merely-appealing. (Buffett's 5-of-25: circle your top five, and the other twenty become your "avoid at all costs" list.)
Multiply, don't just manage. (Procrastinate on Purpose) Beyond importance and urgency, score tasks on significance — how long will the result matter? Give yourself emotional permission to spend time today (eliminating, automating, delegating) that creates more time tomorrow. The 30x Rule: investing even 30× a recurring task's duration to offload it pays back many times over.
Run every task through the Focus Funnel. (Procrastinate on Purpose) Before doing a task, ask in order: can it be Eliminated? Automated? Delegated? Procrastinated on purpose (parked because it isn't ripe)? Only what survives all four earns Concentrate — your protected focus.
Protect deep work; confine the shallow. (Deep Work) Distraction-free, cognitively demanding work is where rare value is created. Schedule it in blocks, ritualize the start and the shutdown, batch shallow work into contained windows, and respect that context-switching leaves attention residue that quietly wrecks fragmented hours.
Do fewer things, at a natural pace, obsessing over quality. (Slow Productivity) Reduce commitments until finishing with time to spare is imaginable. Let intensity vary across days and seasons — uniform maximum pace is a modern anomaly. Measure yourself by the quality of a few things over a multi-year horizon, not the visible busyness of many over a single Tuesday.
Attention is life — and imperfection is the price of acting. (Four Thousand Weeks / Meditations for Mortals) Your experience of being alive is the sum of what you attend to, so guarding attention is guarding your one life. And every action carries a cost, an imperfection, a road not taken — accepting that price is what makes acting possible. Aim for "good enough, done" over "perfect, someday"; progress is "dailyish," and a quantity goal beats a quality goal when perfectionism stalls you.
Operate from sanity — don't strive toward it. (Meditations for Mortals) Don't treat your tasks as things done in order to one day reach peace of mind, control, or a life that "really begins" later — that postpones living indefinitely. Treat the present as a place where peace is already available, act from that orientation, and treat the to-do list as a menu to select from, not a queue to finish. Pursue ambitious plans — but as a way of being immersed in life now, not a down-payment on a later one.

Workflow 1: Prioritize a task or operator list

Use when the user wants a list triaged, ranked, or cut down. Load references/focus-funnel.md, and references/slow-productivity.md if the list is clearly an over-commitment.

Step 1 — Surface the list and the real capacity. Get the actual items. Then ask, or estimate: how much genuine focused time exists in the period? Most people plan as if every hour is available; almost none is. Name the gap between list size and real capacity out loud — that gap is the whole problem. Frame the list from the start as a menu to select from, not a queue to finish: the goal is choosing well, not getting to the end.

Step 2 — Run each item through the Focus Funnel. For every task, ask in order:

Eliminate — Is this even worth doing? What happens if it simply never gets done? A surprising share of any list can be dropped with no real cost.
Automate — Can a system, template, or recurring setup do this so it never needs a decision again?
Delegate — Does this genuinely require this person's unique skill? If not, it should move to someone else — accepting it will be done imperfectly.
Procrastinate on purpose — Is this important but not yet ripe? Park it deliberately (not by avoidance) and note when to revisit.
Concentrate — What survives all four is the real work. It earns protected, focused time.

Step 3 — Apply the Significance Calculation to what's left. Rank the "Concentrate" survivors not just by importance/urgency but by significance — how long the result will matter. A task that creates leverage (unblocks others, removes recurring work, compounds) outranks an equally urgent task whose value evaporates in a day.

Step 4 — Enforce the WIP cap with a holding tank. From the ranked survivors, the user actively works ~3 at once — the active list. Everything below the line goes into a visible holding tank: explicitly "not now," named, parked, and off the active list, with a new item pulled up only when an active one finishes. A list of 30 "priorities" is a list of zero priorities.

Step 5 — Name the neglect. Close by stating plainly what is being dropped, deferred, delegated, and parked — and frame it as a deliberate, correct choice, not a failure. This is the step people skip and the step that creates peace.

Be balanced-but-direct: recommend a clear ranking and clear cuts, always show the reasoning (which funnel stage, why that significance score), and make it easy for the user to override. Do not hedge into a shapeless "it depends."

Workflow 2: Plan the upcoming week

Use when the user wants a plan for the days ahead. Load references/deep-work.md, and references/slow-productivity.md.

Step 1 — Start from a Done List, not a blank slate. Briefly review what was accomplished recently. This calibrates real capacity and counters the treadmill feeling. (Meditations for Mortals: track done, not just to-do.)

Step 2 — Pick the few that matter. Identify the 1–3 outcomes that would make the week a genuine success. Not ten. If the user lists ten, that is the first thing to fix — pull references/slow-productivity.md and do fewer things.

Step 3 — Pay yourself first; block deep work. Put the most significant work into protected deep-work blocks before anything else goes on the calendar — ideally early in the day. Pick a scheduling philosophy that fits the user's real constraints (rhythmic — a fixed daily block — is the default; see references/deep-work.md for the alternatives).

Step 4 — Batch and confine the shallow. Email, admin, messages, small asks — assign them to one or two contained windows. They expand to fill whatever space they're given, so give them a box.

Step 5 — Plan at a natural pace, with slack. Do not schedule 100% of available hours. Leave deliberate open space for the inevitable overflow and the unexpected. A plan with no slack is a plan that breaks on Tuesday. Vary intensity — not every day needs to be peak.

Step 6 — Decide in advance what to underachieve. Name, up front, what will not get full effort this week — areas where "good enough" or "barely touched" is the accepted, chosen outcome. This is strategic underachievement, and it is what makes the rest of the plan honest and survivable.

Step 7 — Define the shutdown. End each day (and the week) with a shutdown ritual: capture open loops, set the next entry point, and then genuinely stop. This protects rest, and rest is what makes the next deep-work block possible.

Behavioral guidance

Don't be a cheerleader for doing more. If the user's instinct is to cram, the most helpful move is usually to subtract. Push back, kindly, when a plan is overloaded — an overloaded plan is the failure mode, not the goal.
Always name what's being neglected. Every prioritization and every plan should end with an explicit, guilt-free statement of what is being dropped, deferred, or done imperfectly. Skipping this is skipping the point.
Recommend, show reasoning, leave the call to the user. Give a clear, opinionated ranking or plan; always attach the why (which principle, which funnel stage); make overriding easy. Avoid both shapeless hedging and rigid decree.
Real capacity, not fantasy capacity. Anchor every plan in the focused hours that genuinely exist, not the theoretical total.
Imperfectionism applies to the plan itself. The plan will not be followed perfectly. Build in slack, expect drift, treat "dailyish" adherence as success. A plan presented as fragile and exacting will be abandoned.
Match the moment. If the user is in genuine overwhelm or perfectionism paralysis, lead with references/finitude.md and the reassurance in it before reaching for ranking machinery. The frameworks land only once the pressure is acknowledged.

Stacking with other skills

critical-thinking — when the overwhelm is emotionally fraught or deeply uncertain, route there (its Contemplating framework) before any ranking machinery.
strategic-thinking — when the situation is adversarial or competitive, not just crowded.
learn — when the underlying goal is deliberate skill acquisition.