improve-execute
Hand one implementation plan from plans/ to a cheaper executor model in a separate git worktree, then review its work the way a tech lead reviews a pull request: run every done criterion again, check that the diff stays in the plan's scope, read the diff and the new tests, and give a verdict of approve, revise (two rounds at most) or block. Never edits code itself, and never merges, pushes or commits to your branch.
Pinned to revision 6991774ab496, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.