strong agree. I always have the LLM put an actual markdown doc in a docs/plans/ folder before starting work. I often, but not always review it.
Aside: it also helps for code review! Review bots can point out the diff between plan and implementation.
Some examples for the curious: https://github.com/sociotechnica-org/symphony-ts/tree/main/d...
[flagged]
It's one of the things that surprised me when I first started using the compound engineering plugin.
I've been considering adding a review gate with a reviewing model solely tasked with identifying gaps between the plan and the implementation.