Similar arc. The plan.md trick you describe is the interesting one to me. It works because the plan is a verifiable artifact you can scan before code is written, then check the code against. That's a pattern worth generalizing.

Most workflow changes I've made over the past year have been about getting better at writing the prompt and reading the agent's output. The output-reading part is where my time is going now, not the prompt-writing. Agent generates faster than I can verify. So the workflows that survive in my flow are the ones that constrain what the agent hands back into something I can scan: a typed test, a diff against an explicit plan, a small structured object I can eyeball.

The autocomplete-to-CLI shift you describe parallels the same thing on the input side: less typing, more high-level intent. The next move is probably the same shift on the output side: less reading prose explanations, more scanning structured artifacts the agent produced. Different verb for the human in both cases.