Claude code for large work flows

For large work flows which takes time

Steps to fallow long Claude Code sessions comes down to a handful of habits:

1. Scope your work first, then steer.
   • Ask for Detailed Plan, review thoroughly, edit and make it precise and clear
2. Direct your compaction so the summary keeps what matters.
   • prompt: /compact
     • Ex: /compact focus on failed test cases due to updated code
3. Use the rewind menu to course correct when Claude drifts.
   • prompt: /rewind => takes to last check point
     • Restore code and conversation - roll back both together.
     • Restore conversation - roll back just the chat.
     • Restore code - roll back just the files.
     • Summarize from here - summarizes everything after the checkpoint. Great if you had a side conversation and just want to free up some space.
     • Summarize up to here - summarizes everything before the checkpoint. Great when you had a long setup phase you want to compress, but you want to keep the implementation parts intact.
4. Set a goal when you can describe “done” better than you can describe the steps.
   • prompt: /goal => you give it a stop condition, and it keeps running turns until that condition is met (or fails). It’s not a fixed loop count
     • Ex: /goal CHANGELOG.md has an entry for every PR merged this week
   • prompt to cancel it: /goal clear
   • prompt: /loop => runs on a time interval rather than a specific success condition, good for recurring/watchdog-style tasks, not “run until done” tasks
     • Ex: /loop 3m run npm run build and report any errors
   • To stop loop: Press esc button
   • a loop condition isn’t something you set inside /goal as a separate config — the condition is the goal text itself, phrased as something checkable
5. Run parallel work in work trees.