How I use Claude Code: Separation of planning and execution
1–10 of 630 posts
Re: How I use Claude Code: Separation of planning and execution
#2[flagged]
Re: How I use Claude Code: Separation of planning and execution
#3I do something very similar, also with Claude and Codex, because the workflow is controlled by me, not by the tool. But instead of plan.md I use a ticket system basically like ticket__.md where I let the agent create the ticket from a chat, correct and annotate it afterwards and send it back, sometimes to a new agent instance. This workflow helps me keeping track of what has been done over time in the projects I work on. Also this approach does not need any „real“ ticket system tooling/mcp/skill/whatever since it works purely on text files.
Re: How I use Claude Code: Separation of planning and execution
#4Regarding inline notes, I use a specific format in the `/plan` command, by using th `ME:` prefix.
https://github.com/srid/AI/blob/master/commands/plan.md#2-pl...
It works very similar to Antigravity's plan document comment-refine cycle.
Re: How I use Claude Code: Separation of planning and execution
#5The plan document and todo are an artifact of context size limits. I use them too because it allows using /reset and then continuing.
Re: How I use Claude Code: Separation of planning and execution
#6[flagged]
Please don't be knee-jerk dismissive of posts. Absolute nothing about this article looks "LLM-generated style" to me.
Re: How I use Claude Code: Separation of planning and execution
#7Kiro's spec-based development looks identical.
It looks verbose but it defines the requirements based on your input, and when you approve it then it defines a design, and (again) when you approve it then it defines an implementation plan (a series of tasks.)
Re: How I use Claude Code: Separation of planning and execution
#8[deleted]
Re: How I use Claude Code: Separation of planning and execution
#9This all looks fine for someone who can't code, but for anyone with even a moderate amount of experience as a developer all this planning and checking and prompting and orchestrating is far more work than just writing the code yourself.
There's no winner for "least amount of code written regardless of productivity outcomes.", except for maybe Anthropic's bank account.
Re: How I use Claude Code: Separation of planning and execution
#10I do something very similar, also with Claude and Codex, because the workflow is controlled by me, not by the tool. But instead of plan.md I use a ticket system basically like ticket_ _ .md where I let the agent create the ticket from a chat, correct and annotate it afterwards and send it back, sometimes to a new agent instance. This workflow helps me keeping track of what has been done over time in the projects I wo…
+1 to creating tickets by simply asking the agent to. It's worked great and larger tasks can be broken down into smaller subtasks that could reasonably be completed in a single context window, so you rarely every have to deal with compaction. Especially in the last few months since Claude's gotten good at dispatching agents to handle tasks if you ask it to, I can plan large changes that span multilpe tickets and tell claude to dispatch agents as needed to handle them (which it will do in parallel if they mostly touch different files), keeping the main chat relatively clean for orchestration and validation work.