Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How I use Claude Code: Separation of planning and execution

boristane.com

Post reply on HN
Print view View original

581–590 of 630 posts

Re: How I use Claude Code: Separation of planning and execution

#581

Post by maxnevermind »

sparin9 wrote: post #418

I think the real value here isn’t “planning vs not planning,” it’s forcing the model to surface its assumptions before they harden into code. LLMs don’t usually fail at syntax. They fail at invisible assumptions about architecture, constraints, invariants, etc. A written plan becomes a debugging surface for those assumptions.

Yeap, I recently came to realization that is useful to think about LLMs as assumption engines. They have trillions of those and fill the gaps when they see the need. As I understand, assumptions are supposedly based on industry standards, If those deviate from what you are trying to build then you might start having problems, like when you try to implement a solution which is not "googlable", LLM will try to assume some standard way to do it and will keep pushing it, then you have to provide more context, but if you have to spend too much time on providing the context, then you might not save that much time in the end.

Re: How I use Claude Code: Separation of planning and execution

#582

Post by ramoz »

ramoz wrote: post #520
gary17the wrote: post #322

> Read deeply, write a plan, annotate the plan until it’s right, then let Claude execute the whole thing without stopping, checking types along the way. As others have already noted, this workflow is exactly what the Google Antigravity agent (based off Visual Studio Code) has been created for. Antigravity even includes specialized UI for a user to annotate selected portions of an LLM-generated plan before iterating i…

With hooks you can achieve a similar UI that can do what antigravity does just as much & better. Search "claude code plan annotations plugin" and youll come across some.

example: https://github.com/backnotprop/plannotator

Re: How I use Claude Code: Separation of planning and execution

#583

Post by energy123 »

bavell wrote: post #487
gehsty wrote: post #313

Earlier quoted context omitted.

I think this was more of a thing on older models. Since I started using Opus 4.5 I have not felt the need to do this.

Anthropic got rid of controlling the thinking budget by parsing your prompt - now it's a setting in /config.

They never parsed your prompt. The magic word reduces the probability that the token corresponding to the end of chain-of-thought will be emitted, which increases test-time compute.

Re: How I use Claude Code: Separation of planning and execution

#585

Post by synergy20 »

remify wrote: post #442
sparin9 wrote: post #418

I think the real value here isn’t “planning vs not planning,” it’s forcing the model to surface its assumptions before they harden into code. LLMs don’t usually fail at syntax. They fail at invisible assumptions about architecture, constraints, invariants, etc. A written plan becomes a debugging surface for those assumptions.

Sub agent also helps a lot in that regard. Have an agent do the planning, have an implementation agent do the code and have another one do the review. Clear responsabilities helps a lot. There also blue team / red team that works. The idea is always the same: help LLM to reason properly with less and more clear instructions.

I think claude-code is doing this at the background now

Re: How I use Claude Code: Separation of planning and execution

#586

Post by locknitpicker »

copirate wrote: post #566
locknitpicker wrote: post #543

Earlier quoted context omitted.

> A detailed workflow that's quite different from the other posts I've seen. Seriously? Provide context with a prompt file, prepare a plan in plan mode, and then execute the plan? You get more detailed descriptions of this if you read the introductory how-to guides of tools such as Copilot.

Making the model write a research file, then the plan and iterate on it by editing the plan file, then adding the todo list, then doing the implementation, and doing all that in a single conversation (instead of clearing contexts). There's nothing revolutionary, but yes, it's a workflow that's quite different from other posts I've seen, and especially from Boris' thread that was mentioned which is more like a collect…

> Making the model write a research file

Having LLMs write their prompt files was something that became a thing the moment prompt files became a thing.

> then the plan and iterate on it by editing the plan file, then adding the todo list, then doing the implementation, and doing all that in a single conversation (instead of clearing contexts).

That's literally what planning mode is.

Do yourself a favor and read the announcement of support for planning mode in Visual Studio. Visual Studio code supported it months before.

https://devblogs.microsoft.com/visualstudio/introducing-plan...

Re: How I use Claude Code: Separation of planning and execution

#588

Post by Bishonen88 »

mstkllah wrote: post #427
Bishonen88 wrote: post #255

Earlier quoted context omitted.

It was when I mvp'd it 3 weeks ago. Then I removed it as I was toying with the idea of somehow monetizing it. Then I added a few features which would make monetization impossible (e.g. How the app obtains etf/stock prices live and some other things). I reckon I could remove those and put in gh during the week if I don't forget. The quality of the Web app is SaaS grade IMO. Keyboard shortcuts, cmd+k, natural language…

Would love to check it out too once you put it up.

Here's a sneek peak into how it looks like/what it is. If there's still appetite for the source code, I'll probably drop a gh link by the end of the week: https://streamable.com/amdz92

Re: How I use Claude Code: Separation of planning and execution

#589

Post by Bishonen88 »

PacificSpecific wrote: post #349
Bishonen88 wrote: post #224

Earlier quoted context omitted.

Dunno. My 80k+ LOC personal life planner, with a native android app, eink display view still one shots most features/bugs I encounter. I just open a new instance let it know what I want and 5min later it's done.

If you wouldn't mind sharing more about this in the future I'd love to read about it. I've been thinking about doing something like that myself because I'm one of those people who have tried countless apps but there's always a couple deal breakers that cause me to drop the app. I figured trying to agentically develop a planner app with the exact feature set I need would be an interesting and fun experiment.

same as you, I tried all sorts of apps. Todoist, habitica, fantastical, wunderlist, karakeep and more and more for all sorts of things. All are OK for most users, but none was GREAT for me. That's why I thought to give LLM's a proper spin. Get all the features I want, in the way I want. And anything I can come up with/see on the web over time, I can add myself within minutes instead of waiting for months for some 3rd party to perhaps add it. + No subscription fee.

You can see my app in action here: https://news.ycombinator.com/item?id=47119434

While I can share the code and it might make a good foundation for forks, creating one from scratch with claude's $100 subscription will take ~2-3 weeks to get it into the state you see in the video. And that is me prompting the LLM for ~30-60 minutes most days of those 2-3 weeks.

Post reply on HN