Beyond Code Generation
AI can generate, explain, refactor, and test code — roughly 20% of the lifecycle. Tickets, docs, infrastructure, review, deploys, rollbacks, and monitoring still consume the rest through manual work and context switching.
Ask most teams what "AI in the SDLC" means and they'll point at the editor: the model writes code, explains code, refactors code, generates tests, suggests fixes. All real. All useful. And all of it covers roughly a fifth of what it takes to ship software.
The other eighty percent
Walk through a feature's actual life and count what still happens by hand:
- Tickets — something breaks, a human writes the Jira issue, links it, triages it
- Docs — updated after the fact, when anyone remembers
- Infrastructure — a human runs Terraform or Pulumi from a terminal, context-switching out of the editor to do it
- Architecture review — humans in a meeting
- Deploy and rollback — a human watches the pipeline, and a human decides to roll back
- Monitoring — dashboards, alerts, and a human on call to interpret them
None of this is coding, and none of it went away when the coding got fast. AI coding is not software delivery. The gap between the two is measured in context switches — editor to Jira to Terraform to Grafana and back — and every switch is a human carrying state between tools that don't talk to each other.
Why "add more copilots" doesn't fix it
The obvious move is to automate the other phases the same way: a ticket bot, a deploy bot, a docs bot. But bolt-on automation per phase reproduces the original problem at a new level — you get islands of automation, each with its own context, none aware of the others. The human stops doing the work and starts doing something arguably worse: ferrying context between bots.
This is the state of most "AI-forward" teams today: Copilot in the editor, an AI summarizer in the PR, maybe an AI triage rule in PagerDuty — three disconnected islands. The coding assistant doesn't know what the incident bot learned last night. The PR summarizer doesn't know what the ticket said. Every seam between them is patched by a human copy-pasting.
The real requirement
What the lifecycle needs isn't more assistants — it's continuity: agents that hand work to each other, carrying context forward, with humans stationed at the points where judgment matters. Not a faster editor. A different lifecycle.