Agentic engineering
Professional software work in which coding agents write most of the code while engineers own the specs, the checks, the review and the result.
Simon Willison proposed “vibe engineering” for experienced engineers who use agents while staying “proudly and confidently accountable for the software they produce”, and later noted that agentic engineering is the name that stuck; his Agentic Engineering Patterns guide collects the practices. It is the opposite end from vibe coding, where nobody reads the result.
The skills shift rather than disappear: writing a precise spec or PRP, designing tests and validation, splitting work into tasks agents can finish, reviewing plans and diffs, and knowing when to take the keyboard back. Job ads now ask for it directly, from senior roles that direct agents to software factory setups where agents write all the code.
Sources
- Simon Willison: Vibe engineering simonwillison.net
- Simon Willison: Agentic Engineering Patterns simonwillison.net
Related terms
- Vibe coding: Building by prompting and accepting the result without reading the code closely.
- Spec-driven development: Writing the specification and acceptance tests first, then letting agents implement against them.
- Coding agent: An agent that reads a repository, edits files, runs commands and tests, and opens pull requests.
- Comprehension debt: The growing gap between how much code a system has and how much of it anyone on the team actually understands, a typical cost of fast AI-written code.
- Software factory (AI agents): A pipeline where agents write and fix most of the code while people write specs, set guardrails, design the checks and decide what ships.
- PRP (Product Requirement Prompt): A PRD rewritten for a coding agent: the goal and why, plus the exact files, patterns to follow and commands that prove the work is done.
