Engineering notes that start with a problem
From checks before AI code changes to collaboration across CLIs: understand a problem, inspect evidence and tools, then start small in your own environment.
Documentation reviewed 2026-11-05
Read a problem, then try a tool
What should an AI check before changing code?
Add whitespace handling and a default name to one greeting function. Follow the same three tests from failure to success, connecting requirements, design decisions and execution evidence.
How can different AI CLI sessions collaborate explicitly?
A review request sent to another CLI has no reply. Should you send it again? Follow one illustrative request to separate delivery, acknowledgement, work completion and decisions under uncertainty.