I tried a workflow on my last project and it went really well, so I’m sharing it. What I did: Planning with Opus 5.5 on max effort. I described the whole project and asked it to make a full plan. Splitting into sessions. I had it break the plan into separate sessions, each a self-contained chunk of work. Rating each session. For every session it rated how hard the task was, then told me exactly which model (Haiku, Sonnet or Opus) and which effort level that session needed. Making a build .md file. All of this went into one markdown file covering the plan, the sessions, and the model/effort for each. How I ran it:
- Each session is a new Claude Code conversation.
- I upload the build .md file first so Claude has the full context.
- I set the model and effort the plan recommended, then tell it which session to work on. Why it worked:
- I didn’t burn Opus max on simple stuff like boilerplate, renaming or small fixes. Haiku or Sonnet handled those fine.
- The hard parts got the heavy model and high effort.
- Starting each session fresh with the .md file kept the context clean. I wasn’t dragging one giant conversation along.
- The sessions were consistent because they all worked from the same plan. It’s basically using the smartest model as a project manager and the cheaper models as the workers. Has anyone else tried something like this? I’m curious if you split sessions differently or let Claude pick the model on its own. submitted by /u/Throwaway_SQ2
Originally posted by u/Throwaway_SQ2 on r/ClaudeCode
You must log in or # to comment.