Why does document your processes fail?

The most common reason document your processes fails: 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.

The fix: 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 L-0410). If you can't articulate the trigger or conditions, you've discovered the agent was vaguer than you thought.

The underlying principle is straightforward: Written agent descriptions can be reviewed refined and shared.