Comment by squircle
Have you considered using a README (or a ./docs folder) as a source of truth? I was working in this direction (before and after gaining access to LLMs.) I rolled about half the tooling for this (in Rust and JS) and have proven the effectiveness, at least for my own use cases. But, its so ridiculously fast that... I don't know what to do with it. Make a bunch of open source tools? Launch innumerable SaaS'?
The build step is crucial (along with solid system prompts.) This keeps the human in the loop and makes for something that truly feels like rapid/iterative development. Build steps also allow for checkpoints, and provide for something that, from a layman's perspective, feels like reversible computing.
hmm, yeah a readme would be also a useful thing, because then of course the bot can build out its code based on that, but I was thinking just to do it on a file by file basis at the beginning to get further.