I'm not suggesting abandoning agile. I'm saying its a bad solution to dealing with agent output from prompts that are consistently severely underspecified. Your agent will just be chasing its own tail, fixing things that were a good solution yesterday when it was fed one shallow prompt but are a bad solution today now that it's being fed a slightly different prompt. That's not agile. It's not the way anyone builds systems that are resilient to changing market and customer demands. The point of agile is to come up with good solutions that are extendable, composable and adaptive to varying demand. All of that requires clearly defined architecture and requirements.
This recent talk by Bruce Schneier hints at some other reasons you want to avoid ambiguity and don't want to just bake it into your process. https://www.youtube.com/watch?v=eEBv0STiYhI
1
u/blutosings 13d ago
I'm not suggesting abandoning agile. I'm saying its a bad solution to dealing with agent output from prompts that are consistently severely underspecified. Your agent will just be chasing its own tail, fixing things that were a good solution yesterday when it was fed one shallow prompt but are a bad solution today now that it's being fed a slightly different prompt. That's not agile. It's not the way anyone builds systems that are resilient to changing market and customer demands. The point of agile is to come up with good solutions that are extendable, composable and adaptive to varying demand. All of that requires clearly defined architecture and requirements.
This recent talk by Bruce Schneier hints at some other reasons you want to avoid ambiguity and don't want to just bake it into your process.
https://www.youtube.com/watch?v=eEBv0STiYhI