Treat Sessions Like Branches

You start on the billing refactor, get pulled into the onboarding flow mid-afternoon, and never leave. One session now carries both, plus whatever else came up. By evening the output on either has quietly gotten worse, and it's not obvious why.

Give each workstream its own session instead: /rename labels the current one, --resume reopens a named one by picking it from a list. The billing refactor keeps its own context; the onboarding flow gets another. You walk back into the right one instead of rebuilding it from scratch, or working inside a session that's carrying a second, unrelated job.

It's the same instinct as not doing three unrelated changes on one git branch, not because sessions and branches work the same way underneath, but because mixing unrelated work in one place makes it harder to reason about later, in both cases.

The payoff is not tidiness. In my experience, keeping each session small and on-topic does more for output quality than most prompt-engineering advice, because a smaller, cleaner context tends to produce better results than a large, mixed one.