"Agile was always aiming to solve the wrong problem (that code is the bottleneck)"

No, it aimed to solve the "out specs are bad and we need to iterate faster" problem.

"a massive lie exposed by LLMs"

No. LLMs add no insight about the problem and they expose nothing. They just help to engage this well-known problem with another tool.

> always the poor specs

But that is fundamentally what agile is about. It's not about coding faster, it's the recognition that the specs are incomplete or wrong because fundamentally, a lot of customers cannot tell you what the want until they see it. That's why "build something simple and iterate on it" works. Regardless of how good your spec is, once the coding is done the customer is going to realise that that's not what they actually wanted.

Agile never claimed that.

Agile is about working code instead of hundreds of pages of spec nobody reads.

>It’s always the poor specs, terrible analysis and release constraints that kill projects.

So most of the problems are related to business people and not the development teams? Who would have guessed?