3 ms·
Huh, very much not my experience with plan mode. I use plan mode before almost anything more than truly trivial task because I've found it to be far more effic
by mikkupikku 8mo ago
Huh, very much not my experience with plan mode. I use plan mode before almost anything more than truly trivial task because I've found it to be far more efficient. I want a chance to see and discuss what claude is planning to do before it races off and does the thing, because there are often different approaches and I only sometimes agree with the approach claude would decide on by itself.
- bushido 8mo agoPlanning is great. It's plan mode that is unpredictable in how it discusses it and what it remembers from the discussion. I still have discussions with the agents and agent team members. I just force it to save it in a document in the repo itself and refer back to the document. You can still do the nice parts of clearing context, which is available with plan mode, but you get much better control. At all times, I make the agents work on my workflow, not try and create their own. This comes with a whole lot of trial and error, and real-life experience. There are times when you need a tiger team made up of seniors. And others when you want to give a overzealous mid-level engineer who's fast a concrete plan to execute an important feature in a short amount of time. I'm putting it in non-AI terms because what happens in real life pre-AI is very much what we need to replicate with AI to get the best results. Something which I would have given a bigger team to be done over two to eight sprints will get a different workflow with agent teams or agents than something which I would give a smaller tiger team or a single engineer. They all need a plan. For me plan mode is insufficient 90% of the times. I can appreciate that many people will not want to mess around with workflows as much as I enjoy doing.