From vibe coding to agentic engineering: test-first orchestration
Engineering teams are shifting from vibe coding to disciplined agentic engineering that treats AI as test-driven collaborators and demands spec-first oversight. In a concise critique of “prompt DJ” development, [Roger Wong](https://rogerwong.me/2026/02/agentic-engineering) summarizes Addy Osmani’s call for agentic engineering—engineers orchestrate coding agents, act as architects and reviewers, and enforce spec-first discipline instead of accepting whatever the model returns. [Simon Willison’s](https://simonwillison.net/guides/agentic-engineering-patterns/first-run-the-tests/#atom-everything) “First run the tests” pattern operationalizes this by making a test suite the entry point for any agent, turning TDD into a four‑word prompt and letting agents learn a codebase through its tests. Hands-on workflows show how to scale this in practice, from a [complete greenfield agentic setup](https://www.youtube.com/watch?v=goOZSXmrYQ4&pp=ygUYQUkgY29kaW5nIGFnZW50IHdvcmtmbG93) to [advanced agent teams comparing Claude Code and Codex](https://www.youtube.com/watch?v=7BXZ-qR5cPE&pp=ygUYQUkgY29kaW5nIGFnZW50IHdvcmtmbG93), while case studies like [DumbQuestion.ai](https://dev.to/jagostoni/dumbquestionai--2ee) underline the need for structured backlogs and cost-aware multi‑model choices.