9 published lessons with this tag.
Feedback you only hear once is feedback you will distort, remember selectively, or forget entirely.
Document your process for managing knowledge — not just the knowledge itself. Your system should be explicit enough that you could rebuild it from documentation alone.
Writing down how two ideas relate prevents assuming a connection that does not exist.
Recording what you tested and what happened creates a validation history.
Written agent descriptions can be reviewed refined and shared.
A well-written document delegates explanation, alignment, and decision context to the future.
Record what you changed, why, and what happened — optimization without documentation is gambling.
Retire agents gracefully — document what they did, why they're being retired, and what replaces them.
Documentation should evolve with the agent — outdated docs are worse than no docs.