> and it's likely producing better output to keep a human in the loop rather than trying to solve the world independently and making multiple incorrect assumptions.
I was just discussing this with a co-worker yesterday. I would really like a model (or harness?) that worked with me instead of for me. Walk me through its choices and decisions, let me correct it and guide it along. I would be way more confident in it's output, I would be more familiar with the changes that are being made, and it would make reviewing the final code way easier since I was making the decisions along side it. I'm sure it would also reduce the "brainrot" we're all going to experience the more we hand work to these models.
Those exist and they're called orchestration skill frameworks like Superpowers, GetShitDone, etc.
the "grill" skill from matt pocock is quite nice for this
Aside from the skills mentioned, I recently found that asking the model to create a simple HTML presentation to walk you through it's proposed design can do wonders. Fine tune your prompt to your liking (language style, what to include, what not, etc). Then, read that thing thoroughly, and keep asking questions and iterating on the plan until you fully understand what's about to be built, and are happy with it.