A 90x gain in code output is not a productivity number — it is a structural stress test applied to every downstream process that assumed a human wrote the code. The engineers and teams now working with Claude Code and comparable agents are not slower than they used to be; they are faster at producing artifacts that require more scrutiny, not less. The review burden that results from AI-generated pull requests is qualitatively different from reviewing human-authored code: the volume is higher, the confidence of the generated output is higher, and the reviewer's ability to spot errors is degraded by the sheer pace of throughput.

This is the contradiction at the center of the current agent moment. The gains are real — but they are concentrated at the generation layer while the validation layer remains human-scaled. Teams that have not explicitly restructured around that asymmetry are not moving faster overall; they are accumulating review debt as overnight agents ship code no one has time to read carefully. The engineers who built the previous bottleneck — writing code — are now the new bottleneck, reassigned as judges in a process they did not design.

The validation gap is not just about PR review — it extends into plugin and integration testing, where teams are discovering that the toolchain for building with agents is far more mature than the toolchain for verifying what agents built. A SaaS developer asking how to wire integration tests to an agent-built plugin repo is describing a structural problem, not a configuration question: the generation workflow has documentation, tooling, and community support; the testing workflow is improvised.

This pattern — AI code review becoming the new delivery constraint while generation continues to accelerate — is exactly what earlier stories on agentic AI splitting teams along existing skill lines predicted. The developers with strong testing instincts are now doing the highest-value work in an agent-augmented team; the developers who relied on the act of writing code to surface problems are finding that agents write through problems without pausing. The teams that close that gap first — by treating validation infrastructure as the primary investment, not an afterthought — will be the ones that actually deliver on the velocity promise.