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
- aya-taleb/productivity-skillstheir own version, first seen Nov 1, 2026
- prsolans/claude-skillstheir own version, first seen Oct 15, 2026
- davekilleen/Dextheir own version, first seen Aug 31, 2026
- MoeenNehzati/famulustheir own version, first seen Jul 8, 2026
- talgacapri/pm-ostheir own version, first seen May 23, 2026
- nbirkner/digital-braintheir own version, first seen Apr 12, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- davekilleen/Dex★ 509same name
- MoeenNehzati/famulus★ 4same name
- aya-taleb/productivity-skills★ 1same name
- steptian/skills★ 1same name
- nbirkner/digital-brain★ 0same name
- prsolans/claude-skills★ 0same name
- talgacapri/pm-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- core/AGENTS.mdAGENTS.md
- evals/AGENTS.mdAGENTS.md
- index/AGENTS.mdAGENTS.md
- mcp/AGENTS.mdAGENTS.md
- tools/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- audit-notesSkill
- challenge-planSkill
- change-impactSkill
- clarify-requestSkill
- connect-mcpSkill
- create-teamSkill
- debug-issueSkill
- define-termsSkill
- design-specSkill
- end-of-day-summarySkill
- handover-notesSkill
- join-teamSkill
- merge-workSkill
- migrate-legacy-engineSkill
- personal-setupSkill
- quick-noteSkill
- register-projectsSkill
- repo-mapSkill
- resolve-conflictsSkill
- resume-workSkill
- retrospectiveSkill
- review-changeSkill
- set-profileSkill
- setup-repoSkill
- story-mapSkill
- suggest-skillsSkill
- summarize-filesSkill
- sync-websiteSkill
- trim-agent-docsSkill
- update-pluginSkill
- weekly-reviewSkill
- whats-changedSkill
- write-agent-docsSkill
- write-area-briefSkill
- write-context-docsSkill
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
- Very specific: line 16
If daily/<today>.md already exists, open it, never overwrite it — jump to Step 2.
- Distinctive: line 47
Don't overwrite an existing daily note — ever.
- Very specific: line 48
Don't process the inbox here (that's /weekly-review).
- Very specific: line 49
Don't touch context/ — /daily-plan reads it, /weekly-review restamps it.
“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.
Files
/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 anydue:/deadline:that is today, overdue, or inside the next 3 days.- Yesterday's note (the most recent
daily/*.mdbefore today): unchecked- [ ]items and anything under## 💡 Capturedthat 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-reviewif 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-planreads it,/weekly-reviewrestamps it.
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.

