Lessons / Part 10. Coding agents, commands and skills
65 Review a plan one role at a time
A hostile review of the plan in four passes, one role each, written to its own file with every invented threshold named.
What people usually ask
Review my plan.What comes back
Approval, two minor suggestions, and a note that the plan is well structured.
Ask this instead
Read plan.md, my plan to move the chromatography exports into a database. Review it four times, one role per pass, in this order: the development lead, the data scientist, the project manager, the domain expert (an analytical chemist). Each pass is hostile; its only job is to find what makes the plan fail.
Each finding in three lines: problem, consequence, fix. At least four findings per role, none repeated across roles. No praise.
Separately, list every number the plan sets without a source (a timeout, a sample count, a tolerance, a date) with the line it sits on. Those are thresholds the plan invented.
Write all of it to review.md. Change nothing in plan.md.Attach: plan.md.
Why it works: Each role looks for its own kind of failure, and the list of invented thresholds shows what the plan decided without anyone being asked.
Drafted with Fable 5.1 from my notes; chosen and edited by me.