session-cleanlisted

# /session-clean A check on whether the current chat session can be closed without losing context. It sweeps the whole session for anything left undone, unanswered, or decided only in chat rather than recorded somewhere durable, and reports either that it is safe to delete or what still needs attention. Full procedure: `references/session-clean.md`. Read it before starting — classifying each thread, grouping whatever is better handed off, and picking a destination for the rest are what make the verdict trustworthy. ## Never write anything unprompted This command **proposes and waits**. It puts up the `CLAUDE.md` edits, GitHub issues, or handoffs it thinks are worth making — with a draft of the actual content — and touches nothing until the user confirms. That is not caution for its own sake. The command operates on the user's judgement about what mattered in a conversation, and that judgement is theirs: what looks like an unresolved thread from the transcript may be something they decided against, already know, or don't want recorded. Acting on the sweep's own reading would quietly convert that judgement into commits and issues. ## Scope The whole current chat session, not one repo. If the session touched several repos or projects, findings are routed to each one's own `CLAUDE.md` or issue tracker rather than lumped together. ## Relationship to `/handoff` These are the two halves of ending a session. `/session-clean` asks whether anything durable would be lost by clo