agentleFS
shankerdhandshankerdhand/claude-second-brain/.claude/skills/plan-day/SKILL.md

plan-day

Skill0 starsChanged 2 months agoMITView on GitHub

Turn today's commitments and tasks into a realistic ordered plan. Use when the user invokes /plan-day or asks to plan their day, prioritise, or "what should I do first".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the gathering half of /daily-brief if it hasn't run this session.

    line 10
  2. Very specific:

    Read brain/routines/daily.md for the energy pattern, and brain/identity/goals.md for the current single focus.

    line 11
  3. Distinctive:

    Leave 20% unbooked. Days that are planned to the minute fail by 10am.

    line 38
  4. Very specific:

    Never plan over a non-negotiable from daily.md.

    line 39
  5. Distinctive:

    Don't create tasks or calendar blocks unless asked.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The point is realism. A plan that doesn't fit the day is worse than no plan.

Steps

  1. Run the gathering half of /daily-brief if it hasn't run this session.
  2. Read brain/routines/daily.md for the energy pattern, and brain/identity/goals.md for the current single focus.
  3. Find the actual free blocks between calendar commitments. Subtract the non-negotiables from daily.md. What's left is the real budget — usually much less than expected, and saying so is the job.
  4. Estimate each candidate task honestly. If the tasks total more than the budget, say so explicitly and cut, don't compress.
  5. Match work to energy: hard thinking into the sharp window, admin and calls into the slump.

Output

You have <X> hours of actual working time today, in <n> blocks.

09:30–11:00  <deep work>   → <task> · <why now: it's the focus / it's due>
11:00–11:30  buffer
11:30–12:00  <admin>       → <2–3 small things, batched>
...

NOT TODAY — and that's fine:
- <task> → <when instead>

ONE THING: If only one item gets done today, make it <task>.

Rules

  • Leave 20% unbooked. Days that are planned to the minute fail by 10am.
  • Never plan over a non-negotiable from daily.md.
  • Push back if the day is unrealistic — that's the value, not the schedule itself.
  • Don't create tasks or calendar blocks unless asked. Offer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.