Slash Command

/write-handoff

From Context Handoff

Compile, write, and validate a bounded verified task handoff.

Popularity

Parent stars

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/context-handoff:write-handoff artifact-path

Model invocable

No pre-commands

Tool Access

This command is limited to the following tools:

ReadGrepGlobWriteTaskBash(git:*)Bash(python3:*)

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Write a `context-kit/handoff-v1` artifact for the active repository task.
Manual command execution is authoritative; do not install or simulate lifecycle
hooks.

Resolve the destination in this order:

1. `$ARGUMENTS` when non-empty.
2. `CONTEXT_KIT_HANDOFF_PATH` when set.
3. `.context-kit/handoff.md` under the repository root.

Resolve a relative path from the repository root. Then:

1. Gather repository identity, worktree path, branch, HEAD, worktree status, and
   intended base ref with read-only `git` commands. Normalize the origin remote
   to a stable repository identity. Determine `b...

Command Content

47 lines · ~523 tokens

Stats

LanguagePython

Parent stars1

MaintenanceGood

Last CommitJul 19, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

Tags

Write a context-kit/handoff-v1 artifact for the active repository task. Manual command execution is authoritative; do not install or simulate lifecycle hooks.

Resolve the destination in this order:

$ARGUMENTS when non-empty.
CONTEXT_KIT_HANDOFF_PATH when set.
.context-kit/handoff.md under the repository root.

Resolve a relative path from the repository root. Then:

Gather repository identity, worktree path, branch, HEAD, worktree status, and intended base ref with read-only git commands. Normalize the origin remote to a stable repository identity. Determine base_commit with git merge-base HEAD <base_ref>. If the base ref cannot be determined unambiguously, stop and request it rather than inventing one.
Gather the current task objective, scope boundaries, changed-file inventory, completed outcomes, decisions, unresolved items, proposed next steps, and exact validation commands/results from this session.
Use the verify-before-trust skill or verifier subagent to check claims that will affect the next session.
Invoke the handoff-compiler subagent with all gathered state and provenance. The compiler is read-only and must return only bounded structured Markdown.
Persist the returned Markdown at the resolved destination. Create only the necessary parent directory.

Run:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/validate-handoff.py" "<resolved-path>"

If validation fails, repair the artifact and rerun validation. Do not report success while an invalid artifact remains.

Report the repository-relative artifact path, saved HEAD, base ref, and whether the saved worktree state was clean or dirty. Do not automatically ingest the artifact. If the user separately requests historical retention, finish and validate this command first, then use the memory plugin's /archive-handoff.