Oh, so there's whole _skill_ for that! I now feel a bit silly but I reinvented the wheel during my last lil project and indeed found it very powerful. A varian

Oh, so there's whole _skill_ for that! I now feel a bit silly but I reinvented the wheel during my last lil project and indeed found it very powerful. A variant of it is the "implementation (handover) prompt" when I conclude the planning session with plans and design documents, updated handoff, clean tree and a file for a new Opus implementing orchestrator (unusually do a single, highly specific implementer and a single, highly specific tester). After implementation and task-level tests I end up with a long and very detailed implementation progress ledger and a summary findings from the orchestrator. Then in the new session I do the whole branch tests. Works really well, uses much less tokens than any other approach with more of Opus and very little repetitions/corrections.