dayplan
Skill11 starsChanged 28 days agoMITView on GitHub
Plan the day from open tickets, PRs, and the last day plan into a day-plan file, or wrap up the day and set up tomorrow. Use for /dayplan.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- drewnix/hyperfocustheir own version, first seen Apr 15, 2026
- seaneoliver/claude-code-startertheir own version, first seen Mar 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- drewnix/hyperfocus★ 3same name
- seaneoliver/claude-code-starter★ 2same 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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-mdSkill
- architectSkill
- architecture-mdSkill
- behavioral-testingSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- caidan-modeSkill
- clear-communicationSkill
- code-commentsSkill
- correctSkill
- create-verification-skillSkill
- day-planSkill
- design-systemSkill
- distill-to-skillSkill
- goalSkill
- howSkill
- improve-codebase-architectureSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- lean-ts-patternsSkill
- macos-swift-desktopSkill
- maintain-verification-skillSkill
- modern-cssSkill
- no-use-effectSkill
- progress-reportSkill
- progressSkill
- recallSkill
- reflectSkill
- sharpenSkill
- shipSkill
- show-me-your-workSkill
- simplifySkill
- teach-meSkill
- teachSkill
- technical-writingSkill
- typescript-best-practicesSkill
- typescript-refactoringSkill
- type-system-disciplineSkill
- unslopSkill
- update-clientSkill
- status-updateSkill
- whySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Write tomorrow's starting point into the day-plan file, so the next session can start cold.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Day plan
Two branches: start of day (the default) and wrap-up (the user is ending the day).
Start of day
- Find the time available. Plan around parallel agent work, not human-day estimates.
- Gather: the last day-plan file, open tickets under the active parent ticket, open PRs with their CI and merge state, running jobs, and whatever the last session left unfinished.
- Propose tracks in order of value toward the stated goal. Give each an exit condition, mark which can run in parallel and what needs the user, and flag anything worth dropping.
- Once the user agrees, write
day-plan-YYYY-MM-DD.mdin the project root and mirror its main points into todos. When another agent already owns a day plan there, prefix yours (for exampleexperiments-day-plan-YYYY-MM-DD.md). - Re-read the file after every compaction and whenever the user asks where things stand.
Wrap-up
- List what got done today (merged PRs, results, decisions) and what is still open, from the file and live state.
- Post the plan for tomorrow to the tracker.
- Write tomorrow's starting point into the day-plan file, so the next session can start cold.
- Tell the user what can keep running safely while they are away, and what to stop.
Done when: the file is saved and the user has seen the plan in a few lines.
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
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.