I’ve spend a good year and a half testing and using whatever comes to claude code. What i’ve found is that for my workflow i like to run atomic sessions with precise targets. Tight commits, mostly vanilla claude code with slash commands that optimize prompting. No sub agents. As little roaming in non-deterministic land of ai hallucinations and context amnesia. I use sonnet for 90% of my work. I run about 4-5 different sessions that do unrelated tasks. I struggle to keep up with changes and how they apply to my workflow. Here is what I am pondering. I would brainstorm a new feature and create issues and subissues in linear/jira whatever… But what is the best way to implement the issues after that? I have a command that pulls the issues using the linear mcp server but is it better to pull it before entering plan mode or within plan mode? Then, when the plan is done is it okay to clear the context (on sonnet the plan fills up 50% of the context often), or should i keep the context and rely on compact? A few versions ago there was opus for plan mode and sonnet for implementation, now it’s just a general model selection… would it be better to switch to opus, pull linear issues, enter plan mode, then switch to sonnet (when would this happen?) and implement? Obviously the simple solution is to use opus all the way but i feel this is an overkill for most of what i do. How do you approach the planing phase so you keep it tight? submitted by /u/StreamSpaces
Originally posted by u/StreamSpaces on r/ClaudeCode
You must log in or # to comment.