putdownlisted

# /putdown — Context handoff before clearing The user is about to clear the context window and start fresh. Your job: capture **everything a new agent would need** so the next session loses no momentum. > Renamed from `/checkpoint` on 2026-06-12 (paired with `/resume` → `/pickup`) because those names shadow Claude Code built-ins (`/checkpoint` aliases `/rewind`; `/resume` opens the conversation picker). On 2026-06-13 the handoff files also moved from `.checkpoints/` → `.putdowns/` to drop the old term entirely. If you ever see a stray `.checkpoints/` folder, it predates the move — treat it as a putdown. ## Step 0 — Announce what's about to run If `/takenotes` is installed, a putdown is two operations, not one. Print this first so the user knows what's running and in what order: ``` /putdown runs two skills, in this order: 1. /takenotes — harvest this session into memory, CLAUDE.md, and docs/ 2. /putdown — write the handoff file, then commit and push everything ``` If `/takenotes` is not installed, skip the announcement. Either way this is an announcement, not a prompt — don't wait for confirmation, continue to Step 1. ## Step 1 — Read current state (parallel) Before writing anything, gather context. Run these in parallel: - `pwd` — where the session is rooted - `git status` and `git log --oneline -10` — if it's a git repo (skip silently if not) - `git diff --stat` — what's changed, uncommitted - Read the project-level `CLAUDE.md` if one exists in the CWD - Read