I have been doing this process by hand. Try to do something. Observe friction. Document how to avoid it. Rinse and repeat. It works and raises the quality going forward. Most importantly, the vast majority of my tokens are spent moving my project forward.

I would be extremely leery to use an automated hill-climbing loop, repeating the same inputs, and burning tokens on the same task over and over. That’s not going to move my project forward, and I don’t have unlimited tokens to spend.

Worse, how can I be sure that these agents will follow deterministic definitions of friction and priorities for removing it? I can imagine “write less tests” would remove a lot of friction. I see this just adding another layer, where I now would be documenting the system that writes my documentation. I learned how that is likely to turn out from playing the telephone game as a child: poorly.