> If the planner has truly thought the issue through, properly designed the solution, solved all of the emergent problems, then the final "write" of the code is just a few more output tokens.

For me, what usually creates the high cost of implementation with a larger model is the validation process, not the writing of code.

I would get excited to see it finish writing code with so little usage, but then it would gobble up ten times as many tokens on validation.

I've tried to instruct it to keep the validation light with the intention of doing batches of deep validation after a few tasks, but it couldn't stop itself from doing heavy validation on each task no matter how I rephrased the instructions.