session-end
At session end, write the one-file session baton (docs/session/baton.md): a high-level summary of what this session was about, the goal, and the single next task. Overwrites the file — no change lists
SKILL.md.claude/skills/session-end/SKILL.md
GitHubSession End
Overwrite docs/session/baton.md following docs/session/template.md. Write
nothing else.
Steps
- Read
docs/session/template.mdfor the shape, and the currentdocs/session/baton.mdif it exists — carry its Goal forward. - Overwrite
docs/session/baton.md— never append; it holds only the last session. - Fill each section, then set
_Last updated:_to today's date.
Rules that keep it high-level
- This session: 2–3 sentences of prose. No change list, no file names, no
detail — that lives in
docs/progress.mdand the code. - Goal: the standing objective. Carry it forward unchanged until it is reached.
- Next task: exactly one thing — one paragraph, not a list. If several loom,
pick the next and drop the rest. Write
Nonewhen there is no clear next task. - Read first: the one doc the next session must read. Write
Nonewhen there is nothing.
Boundaries
- Read-only on git — never commit, stage, or push.
- Write only
docs/session/baton.md. For git state anddocs/progress.md, that issession-wrapup. - Write the baton through the
human-writingskill.