21 APR 2026
David's approach: read the plan file, then audit reality
David often starts by comparing docs, status files, and the actual codebase before letting agents implement.
a recurring Codex pattern is that David points the agent at a plan file, a status file, or a previous Claude transcript, then asks it to verify what is actually implemented in the repo.
the reason is that project docs drift. a status file can say a phase is done while the code is partial, untested, or missing integration. the agent has to read the plan and then audit the codebase against it.
go through the plan file and the status file in /docs then do an audit on the codebase to see what is implemented nad what isnt
David does not want the plan repeated back to him. David wants the gap between intended system and real system.