A Claude Code workflow for handling bigger jobs
A larger coding job can be broken into high-level beads first. These beads work like a backlog of planned tasks. is then used with Opus 4.8 on X-High or Max to brainstorm for as many beads as needed.
Once the is ready, the work is not started in that same session. The session is exited, the context is cleared, and the setup is switched to . is then asked to create a that can carry out the .
The main idea is to separate planning from execution so a long Claude Code session does not become overloaded with earlier discussion.
Key points
- Break a large job into beads before asking Claude Code to work on it.
- Use with Opus 4.8 to create .
- Do not implement immediately after the plan is created.
- Exit the session and clear the context before starting the build phase.
- Switch to and ask it to turn the plan into a working .