Question
How do I practice document your processes?
Quick Answer
Pick one agent you already run — a decision rule, a recurring process, a behavioral protocol. Write it down in this format: (1) Name, (2) Trigger — what activates it, (3) Conditions — when it applies and when it doesn't, (4) Actions — the specific steps, in order, (5) Success criteria — how you know it worked.
Time yourself. If it takes more than ten minutes, the agent is probably too broad (see Agent scope should be narrow). If you can't articulate the trigger or conditions, you've discovered the agent was vaguer than you thought.
Common pitfall: Writing a description so vague it could mean anything. 'Be more intentional with my mornings' is not a documented agent — it's an aspiration. A documented agent specifies: when X happens, if Y is true, do Z. If your document doesn't have that structure, you haven't documented the agent. You've written a wish.
This practice connects to Agent Fundamentals — building it as a repeatable habit compounds over time.
Learn more in these lessons
- Document your agents
Written agent descriptions can be reviewed refined and shared.
Go beyond the answer
This topic is part of Your Personal AI Operating System — a guided sequence of 16 lessons.
After completing this path you will run a four-layer personal AI operating system: a persistent context layer (the AI knows your role, standards, and current work), a skill library (your repeated tasks specified once, invoked by name), scheduled routines (recurring work that runs without prompting), and a verification layer (specific, testable, documented agents you actually trust). You own the architecture; the tools become interchangeable.
Start the path →