Yes, regardless of tool, I always create a separate plan doc for larger changes

Will try adding the instructions specific to refactors (i.e. copy/move files, don't rewrite when possible)

I've also found it helpful, especially for certain regressions, to basically create a new branch for any Codex/CC assisted task (even if part of a larger task). Makes it easier to identify regressions due to recent changes (i.e. look at git diff, it worked previously)

Telling the "agent" to manage git leads to more context pollution than I want, so I manage all commits/branches myself, but I'm sure that will change as the tools improve/they do more RL on full-cycle software dev