I used to use the built-in plan functionality pretty religiously because it gave me the opportunity to talk through plans with claude. I’ve got a few decades experience as an engineer so I want to help claude use that knowledge to do better work. Lately I’ve been writing markdown plans into a docs directory instead so that I can go over the file with claude line by line. Pros: Claude code doesn’t have to re-write the whole plan each change I want I get to free-form talk with claude instead of it re-prompting me for the plan every time Plans can be bigger and more fleshed out it seems Claude seems to go deeper into the specifics I get a free log of all of the plans that made up the current state of the project Cons: I think because the plans are bigger, it sometimes thinks there’s just too much to do and it’ll just decide not to do certain things (like it will create the frontend, and backend routes, and then just… not integrate them together lol) I spend WAY more time planning things out now, and get somewhat more fatigued it seems I constantly have to prompt claude to review the plan for inconsistencies and gaps (which might actually be a pro, but it’s more necessary now because it doesn’t seem to take the whole plan into account when I ask for changes and might have discrepancies or opposing sections Anyone else do this? Has it been better or worse than the built-in plan feature? Any idea if there is special handling around the built-in that isn’t applied on markdown plans? Any general tips for getting better output from the plans? submitted by /u/nsjames1
Originally posted by u/nsjames1 on r/ClaudeCode