Keep a Session Focused, and Check Its Working Tree

A billing refactor and an onboarding fix have different requirements. Giving each a named session can make their decisions easier to follow than mixing both conversations.

Use /rename to label the current session and --resume to return to an existing one. On return, verify the working directory, branch, current files and outstanding tests. The session controls recover conversation context; they do not restore the source tree to the state that conversation describes.

Separate sessions can still edit the same checkout. Use separate worktrees when the work needs separate files, and coordinate any shared database, ports or external services.

The branch analogy is useful for keeping tasks distinct. Keep the distinction literal where it matters: a conversation records reasoning, while Git records source changes. A safe resumption checks both.