Install
openclaw skills install long-task-handoffAutomatically create a compact, standardized handoff file for long tasks to enable seamless session restarts or agent transfers without losing context or pro...
openclaw skills install long-task-handoffKeep this skill lightweight. Do not manually reproduce the full handoff template in context. Use the bundled Python manager and keep user-facing messages short.
Detailed protocol is deferred to references/protocol.md. Do not load it during normal operation. Load it only if the manager is unavailable, the skill is being audited or modified, or a manual fallback is required.
Prefer:
python scripts/handoff_manager.py update --workspace . --task "Task name" --event context_compaction --compaction-count N
Installed script paths:
.codex/skills/long-task-handoff/scripts/handoff_manager.py/root/.hermes/skills/software-development/long-task-handoff/scripts/handoff_manager.pyUseful commands:
python scripts/handoff_manager.py create --workspace . --task "Task name"
python scripts/handoff_manager.py update --workspace . --task "Task name" --event context_compaction --compaction-count N
python scripts/handoff_manager.py recover --workspace .
python scripts/handoff_manager.py suggest --compaction-count N --json
python scripts/handoff_manager.py validate handoffs/session-handoff-*.md
Pass rich task facts with --input-json when available. Otherwise pass only concise CLI facts such as --completed, --test-result, --key-file, --unfinished, --next-action, --risk, and --do-not-do.
handoffs/ACTIVE.md.recover before asking the user for context.The user should not need to know the handoff path. A new session prompt like "continue this task" should be enough when ACTIVE.md exists.
The handoff is a restart packet, not a project wiki. Include only current restart-critical state: goal, branch/commit/worktree, delta, tests, key files, unfinished items, next actions, risks, and do-not-do items.
Do not include secrets, .env contents, private keys, long chat logs, stale plans, unverified guesses as facts, or descriptions that conflict with the current workspace. Put durable project knowledge in repo docs and reference it by path.
Do not silently continue. Report the concrete failure, keep the message short, and avoid asking the user to restate context unless recover cannot find or read a handoff.