Angie Jones uses a house-hunting agent to show why an agent is one component in a wider system of tools, files, people and other agents. She starts with the job, boundaries and failure modes before deciding how to build the workflow.
Angie Jones separates reusable skills, structured output schemas, deterministic scripts and focused sub-agents. She suggests using ordinary code for exact calculations, models for interpretation and people for decisions that require authority.
The design keeps decisions in queryable state so interrupted runs can resume without duplicating actions. Angie Jones also treats external content as untrusted, limits permissions, requires approval for consequential actions and documents the system so future maintainers can understand it.
Watch on YouTube
