osc

It's almost once a week I see a very similar approach, with variables for the developer's workflow. Sounds just like what I've been using, and published as a template: github.com/s1ugh34d/osc (It has a results corpus of testing done) Specs that are LLM driven development, behavior addressed. All markdown human written, LLM's can write them too. The result is tight spec outcomes from LLM's assisting workflows. Using massive human software specs was great with human developers, but with "clankers" the problem is context. How to wrap software contract context into a markdown file. Works for me, I can have Claude make a osc, review it, amend it, and build a simple solution that has verifiable outcomes. This SpecDD is very similar, doesn't really need to book of documentation, just a guide really.

Seems the markdown input, code output is a very common theme, I use OpenSoucreContracts(https://github.com/s1ugh34d/osc) to have LLM's build software, but building the harness into the contracts is elegant. Combined with prose I sort of have this. With LLM's and the sandbox life, software generation is coming.