agentleFS
marinvchmarinvch/Cortex/skills/daily-plan/SKILL.md

daily-plan

Skill1 starsChanged 18 days agoMITView on GitHub

Open today's vault note and surface the priorities, what's due and what is still open.

7 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

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    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:

    If daily/<today>.md already exists, open it, never overwrite it — jump to Step 2.

    line 16
  2. Distinctive:

    Don't overwrite an existing daily note — ever.

    line 47
  3. Very specific:

    Don't process the inbox here (that's /weekly-review).

    line 48
  4. Very specific:

    Don't touch context/ — /daily-plan reads it, /weekly-review restamps it.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 6 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

/daily-plan — open the day

One note per day, daily/YYYY-MM-DD.md. Fast: create it, brief the user, stop. This is a launchpad, not a review — that's /weekly-review's job.

Step 1 — Create today's note (idempotent)

If daily/<today>.md already exists, open it, never overwrite it — jump to Step 2.

Otherwise create it from templates/daily.md, replacing {{date}} with today's date (YYYY-MM-DD). Create daily/ if it doesn't exist yet.

Step 2 — Gather the brief (read-only)

  • context/current-focus.md — what this week is supposed to be about.
  • context/priorities.md — the standing priorities, if present.
  • projects/*.md — any - [ ] under ## Next actions, plus any due: / deadline: that is today, overdue, or inside the next 3 days.
  • Yesterday's note (the most recent daily/*.md before today): unchecked - [ ] items and anything under ## 💡 Captured that never got processed.

Step 3 — Propose the Top 3

Fill ## 🎯 Top 3 today with a proposal, drawn from focus + due items + yesterday's leftovers. Show it and ask the user to confirm or swap. Never invent work that isn't in the vault — if there is nothing to draw on, leave the boxes empty and say so.

Carry forward yesterday's unchecked items only if the user wants them; a stale checkbox copied forward every morning is noise, not a plan.

Step 4 — Brief and stop

Reply with, at most:

  • today's Top 3,
  • anything due or overdue (say which project),
  • one line on unprocessed captures (N items still in the inbox — suggest /weekly-review if it is over ~10, or if the last review was more than a week ago).

Then stop. Don't reorganize, don't rewrite notes, don't create projects.

Don't

  • Don't overwrite an existing daily note — ever. Captures live there.
  • Don't process the inbox here (that's /weekly-review).
  • Don't touch context/ — /daily-plan reads it, /weekly-review restamps it.

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.

Reviews can't be read right now.

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.