notes
Skill9 starsChanged 27 days agoMITView on GitHub
Write the notes of the handoff file: goal, done, decisions and why, open questions, next action. Use before a long break, before /clear, or when the user asks to save progress or leave notes. Everything else in the file is already written by the hooks.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- arch3rPro/ark-spacetheir own version, first seen Nov 8, 2026
- adeonir/agent-skillstheir own version, first seen Nov 6, 2026
- blogminhquy/javis-ostheir own version, first seen Nov 5, 2026
- letsloose501/sqs-agent-memorytheir own version, first seen Nov 3, 2026
- yourbeckett/beckett-for-claudetheir own version, first seen Nov 1, 2026
- baney75/myelinatetheir own version, first seen Oct 20, 2026
Used with
Projects with it also use brainstorm.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- blogminhquy/javis-os★ 711same name
- howells/fiction★ 23same name
- microsoft/PilotSwarm★ 14same name
- adeonir/agent-skills★ 8same name
- phanghonghao/THU-Awesome-Skills★ 8same name
- baney75/myelinate★ 6same name
- DoKu67/claude-code-skils★ 4same name
- jholhewres/devclaw-skills★ 4same name
- TTflysky/sirenhuisuo★ 4same name
- letsloose501/sqs-agent-memory★ 2same name
11 more not listed
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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
1
Distinctive
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 17
Write your notes into that file, replacing its content: plain markdown, no marker lines.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Handoff notes
The handoff plugin already writes a file for this session after every reply. Your job is to fill in the one block it cannot write itself.
- Find the notes file of this session's thread:
It prints a path under"${CLAUDE_PLUGIN_ROOT}/scripts/handoff-path.sh" --notes.claude/handoffs/.state/(created on first use). If the script says the session has no handoff file yet, say so and stop. Write your notes into that file, replacing its content: plain markdown, no marker lines. The Stop hook copies it into the notes block of the handoff file after every reply. Use these headings, skip any that are empty:
- Goal: what the user is trying to achieve, in one or two sentences.
- Done: what is finished and verified (tests, runs), and what was not verified.
- In progress: what is half-done and where it stands.
- Decisions: each with the reason.
- Rejected: options considered and why they were dropped, so the next session does not repeat them.
- Open questions / blockers: what needs the user's answer or an external input.
- Next action: one step that is startable without thinking: the file and line to open, or the exact command to run.
- Next steps: the ordered list after that.
- Gotchas: non-obvious facts about the code or environment learned in this session.
Do not repeat what the file already captures automatically (the request list, file lists, git state, the compaction summary if there is one). Stay under about 60 lines. Never write secrets (keys, tokens, passwords) into the notes: the file is plain text on disk and is injected into later sessions.
- Tell the user in one line that the notes are saved and will appear in the handoff file after this reply.
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.