Andrew Orobator argues that experienced engineers carry decisions about code quality, ownership and risk that a fresh coding agent cannot infer from an empty context window. He proposes making that judgment reusable through skills, worklogs and review personas, so agents and newer team members can apply it across sessions and projects.
Andrew Orobator treats verification as the boundary between a coding aid and a system trusted to work with greater autonomy. He describes a ladder of builds, tests, visual checks and production signals, with human review of the proof. His feature-flag cleanup agent first scores candidate changes against rollout and component risks, then drafts only safer mechanical cleanups for his review.
Andrew Orobator warns that a guardrail an agent can bypass or authorize for itself is weak. He recommends hard gates at the relevant control point, narrow specialist agents and a review loop that keeps skills current as the codebase changes. His aim is to scale organizational judgment while humans retain approval and merge decisions.
Watch on YouTube
