What does it mean that agent inheritance?

New agents can inherit properties and patterns from existing successful agents rather than being built from scratch.

Example: A project manager has spent two years developing a reliable weekly review agent — every Sunday evening, she sits at the same desk, opens a specific template, reviews her calendar and task list, identifies the three most important outcomes for the coming week, and closes the laptop by 8 PM. The agent fires consistently. Its trigger is clear (Sunday 6 PM), its environment is controlled (home office, no notifications), and its output is specific (three written priorities). When she gets promoted and needs to manage a larger team, she needs a new agent: a monthly strategic review. Rather than designing this agent from nothing, she inherits from her weekly review. The monthly review uses the same physical environment (home office, notifications off), the same structural template (calendar scan, priority identification, written output), and the same time-bounded format (two hours maximum). What changes is the scope — monthly instead of weekly, strategic themes instead of tactical tasks, team outcomes instead of personal ones. The new agent does not need a fragile first thirty days of establishment. It inherits the environmental cues, the procedural scaffolding, and the self-discipline infrastructure that the weekly review already proved. Within two cycles, the monthly review is firing reliably — not because it was easy to build, but because it was built on components that were already working.

Try this: Identify one of your most reliable existing agents — a habit, routine, or behavioral pattern that fires consistently and produces good results. Write down its core components: (1) the trigger that activates it, (2) the environment it operates in, (3) the sequence of steps it follows, (4) the output it produces, and (5) any supporting conditions that keep it reliable. Now identify a new agent you want to build — a behavior or routine you have been struggling to establish. For each of the five components you listed, ask: Can I inherit this from my existing agent? Can I use the same trigger, the same environment, the same structural sequence, or the same supporting conditions? Draft a design for the new agent that explicitly inherits at least two components from the proven one. The goal is not to copy the old agent wholesale — it is to give the new agent a foundation of already-working infrastructure so it does not have to prove everything from scratch.