I don't see how this is 'radically different' given that Claude Code literally has a planning mode.

This is my workflow as well, with the big caveat that 80% of 'work' doesn't require substantive planning, we're making relatively straight forward changes.

Edit: there is nothing fundamentally different about 'annotating offline' in an MD vs in the CLI and iterating until the plan is clear. It's a UI choice.

Spec Driven Coding with AI is very well established, so working from a plan, or spec (they can be somewhat different) is not novel.

This is conventional CC use.

▲

dack 6 hours ago | parent [-]

last i checked, you can't annotate inline with planning mode. you have to type a lot to explain precisely what needs to change, and then it re-presents you with a plan (which may or may not have changed something else).

i like the idea of having an actual document because you could actually compare the before and after versions if you wanted to confirm things changed as intended when you gave feedback

	▲	bluegatty 6 hours ago \| parent \| next [-]
		'Giving precise feedback on a plan' is literally annotating the plan. It comes back to you with an update for verification. You ask it to 'write the plan' as matter of good practice. What the author is describing is conventional usage of claude code.
	▲	gitaarik 5 hours ago \| parent \| prev [-]
		A plan is just a file you can edit and then tell CC to check your annotations