And what about testing? Your relentless coding agents could write massive test suites to cover every aspect of the implementation, meaning you could create something from scratch every iteration, as long as the tests pass. If we instruct the agent to write tests that cover the entire specification — unit tests, integration tests, and even end-to-end tests — could that become the definition of the application? Does agentic coding finally bring to fruition the dream of test-driven development?

I mean, can you, at this point, think of a reason not to have your coding agent write a complete test suite? If you have complete test coverage — the very thing Uncle Bob Martin and Kent Beck dream about in their sleep — do you even need to worry about new implementations? A complete test suite will obviously make the transition from the development phase to the maintenance phase much smoother. And a coding agent will never balk at writing more tests. 

An Agentic manifesto

And if we are developing a new methodology, what becomes the bottleneck? You might think that updating the specification based on feedback would become the choke point. But I could envision having extensive discussions with the customer, recording those sessions, then having AI listen to the recordings and update the specification based on what it hears.