How it differs from the SDLC
The traditional software development life cycle assumes humans write the code and the scarce resource is engineering hours. AIDLC assumes agents write most of the code and the scarce resources become intent, judgment and review capacity.
The stages rhyme — plan, build, test, ship, operate — but the weight shifts. Specifying what you want clearly and reviewing what came back become the real work; the typing in the middle is increasingly automated.
Where the bottleneck moves
When generation is cheap and fast, throughput is no longer limited by how quickly you can write code — it is limited by how quickly you can decide what to build and verify that what came back is correct. AIDLC is really a discipline for managing that new bottleneck: clear intent in, trustworthy review out.