a prompt I've been using a lot recently: implement <SPEC> and while you do, keep a running implementation-notes.html file (or markdown) with decisions you had to make weren't in the spec, things you had to change, tradeoffs you had to make or anything else I should know

Ummm It more looks like a temporary band-aid solution because Claude can't operate on its own plan. The Opus 4.7 hype was so attached to the plan, and now this shows we're not there yet. By the way, using a hook to classify with Haiku and logging responses in fire-and-forget mode is much better than forcing the model to keep track and note and consume more tokens.