> how people mostly use whiteboard today is: plan -> approve -> agent codes -> use whiteboard to explain the code.

I guess it's interesting and useful for now, but I don't think people are going to work at the code level much longer.

In my opinion current coding agents + automatic review systems are already at superhuman reliability during the implementation phase (as in they will not fail something in the plan during implementation and not tell you about it, so there's no need to look at the actual code beyond maybe a cursory glance). I literally just use plan mode + CC's /code-review in each task so it's not like I'm doing anything special. So I think the main human interaction surfaces to target in the future will be in the planning process.

> So I think the main human interaction surfaces to target in the future will be in the planning process.

yes, agreed. we're working on more stuff in that direction (a plan / scratchpad mode), but what i personally like the most is eliminating / shrinking the plan/review gap.

i think reviewing a plan without an implementation doesn't feel that useful anymore, at least to me, because key tradeoffs often only surface during implementation that effect the top-level spec.

in some sense, the code writing process is just a cheap effort which makes the spec better and more thorough?