noteslisted

End-of-session documentation sweep. Use when the user types /notes, says "take notes", "update the docs", "write up the session", or at the end of ANY work session - including in a fresh repo with no docs yet - to capture everything completed, learned, resolved, decided, planned, implemented, or discovered into the repo's living docs (SPEC.md, README.md, tasks/plan.md, tasks/todo.md, created if missing), enforce the hot-file size budgets, and roll finished work into tasks/completed/, the per-date cold-storage folder. Docs only - it never commits or pushes; a whole-session closeout that also commits belongs to wrap-up, and promoting knowledge to permanent memory belongs to reflect. A dictated one-line edit to a README is a plain edit, not a sweep.
thefilesareinthecomputer/dotagents · ★ 0 · AI & Automation · score 72

Install: claude install-skill thefilesareinthecomputer/dotagents

# Notes - session documentation sweep A ping to stop and write down what this session actually produced, then fold it into the repo's living documentation so the next session (yours or another agent's) starts from current truth instead of stale files. Run this when invoked as `/notes`, when the user asks to "take notes" / "update the docs" / "write up the session", or proactively when wrapping up substantive work. **The sweep runs once, forward.** Steps 3 to 5 settle the `tasks/` bundle. Step 6 then checks `README.md` and `SPEC.md` for claims the session made false, and is the only step that touches them. Finish a step and do not reopen it: if step 6 surfaces something that belongs in `plan.md`, add the line and keep going rather than restarting the bundle. Root docs judged against an unsettled plan, then judged again once it settles, is the rework this order exists to prevent. If step 7's re-measure leaves a hot file over budget, trimming it further is a bounded correction and is fine: a late trim to `plan.md` or `todo.md` cannot invalidate a root doc. Reopening `README.md` or `SPEC.md` is not bounded, so it means re-running step 6's heading map first. ## Step 1 - Reconstruct the session Before touching any file, think back over the whole session and list, concretely: - **Completed** - what got built, fixed, or shipped (with file paths). - **Learned / discovered** - non-obvious facts about the codebase, tools, or environment that weren't written down anywhere. - **R