hermit-hand-back

To queue a next task after a takeover, the Skill optionally writes your instructions to NEXT-TASK.md. This file prepares the hermit for the next work cycle before the Docker container restarts.

To update the hermit session state, the Skill modifies SHELL.md with the takeover summary and clears the takeover timestamp. This ensures the session accurately reflects progress before the next autonomous operation.

Yes, you need a Docker environment to hand back control because the Skill restarts the hermit Docker container to resume autonomous operation. It operates locally after a takeover session to prepare the hermit for the next task.

The best way to automate the hand-back phase after a hermit takeover is using a dedicated automation Skill. It automatically summarizes git activity, queues next tasks via NEXT-TASK.md, and restarts the Docker container without manual intervention.

You should not use an automated container restart if you need to manually inspect git diffs or intervene before autonomous operation resumes. The Skill clears the takeover timestamp and immediately restarts the hermit Docker container upon execution.