Haha this is surprisingly and exactly how I use claude as well. Quite fascinating that we independently discovered the same workflow.

I maintain two directories: "docs/proposals" (for the research md files) and "docs/plans" (for the planning md files). For complex research files, I typically break them down into multiple planning md files so claude can implement one at a time.

A small difference in my workflow is that I use subagents during implementation to avoid context from filling up quickly.

▲

brendanmc6 3 hours ago | parent [-]

Same, I formalized a similar workflow for my team (oriented around feature requirement docs), I am thinking about fully productizing it and am looking to for feedback - https://acai.sh

Even if the product doesn’t resonate I think I’ve stumbled on some ideas you might find useful^

I do think spec-driven development is where this all goes. Still making up my mind though.

	▲	puchatek 2 hours ago \| parent \| next [-]
		Spec-driven looks very much like what the author describes. He may have some tweaks of his own but they could just as well be coded into the artifacts that something like OpenSpec produces.
	▲	clouedoc 3 hours ago \| parent \| prev [-]
		This is basically long-lived specs that are used as tests to check that the product still adheres to the original idea that you wanted to implement, right? This inspired me to finally write good old playwright tests for my website :).