domains / agent-tooling / session-handoff / handoff

handoff

Skill card

combined

The four copies overlap on the goal of transferring context to a fresh agent, but they disagree on the artifact, the storage location, and the required steps. mattpocock/skills produces a compact document in the OS temp directory with a 'suggested skills' section. davidondrej/skills produces a structured template in a fenced code block saved to a temp file or HANDOFF.md, with explicit core principles and a verification prompt. davepoon/buildwithclaude is a multi-artifact ritual that writes to ~/.origin/sessions/ and calls MCP tools for granular memory captures. openclaw/agent-skills produces a clipboard-ready prompt that avoids filesystem paths and instructs the receiving agent to perform an independent review. Because each copy contains material steps or constraints the others lack, crowning one would hide real alternatives.

Repositories

Other copies

Combined skill

# Handoff

Capture the context a fresh agent needs to continue without re-asking, re-discovering, or repeating mistakes.

## Core Principles

1. **Describe state.** Write "Auth is implemented; logout is not started," not "Implement logout next." The next agent chooses actions from the context.
2. **Link existing artifacts.** Reference PRDs, plans, ADRs, issues, commits, diffs, and design docs by path or URL instead of copying their content.
3. **Preserve why.** Capture decisions, rejected approaches, and failures that code alone cannot explain.
4. **Require verification.** Present claims as context to check against the actual code, not facts to trust blindly.
5. **Redact secrets and PII.** Never include keys, tokens, passwords, or personal data. Name credential locations (e.g. ".env.local, not committed"), never values.
6. **Keep only useful context.** Omit obvious, redundant, or explanatory material recoverable from code or project configuration.

## Procedure

1. Read existing project instructions (AGENTS.md or equivalent). Keep the handoff session-specific; do not repeat those instructions.
2. Read and update any prior handoff instead of starting from scratch.
3. Treat user-supplied arguments as the next session's focus.
4. Fill every template section; mark empty sections `None`.
5. Output the handoff in one fenced code block and save the same content as described under **File Output**.

## Output Format

Use this template inside a single fenced code block:

```
# HANDOFF: <short title of the work>
Generated: <timestamp> · Session focus: <one line>

## 1. Goal
<The overall objective in 1–3 sentences.>

## 2. Why This Matters / Background
<Motivation, intended users, timing, constraints, and hard requirements not already in project configuration.>

## 3. Current State
<What is DONE, PARTIAL, and NOT STARTED. Describe status, not actions:>

## 4. Key Decisions (and why)
<Choices and reasoning, especially what cannot be recovered from code.>

## 5. Traps & Dead Ends
<Failed approaches and pitfalls the next agent might repeat, with reasons.>

## 6. Relevant Files & Pointers
<Paths with line ranges and specific contents; link external artifacts instead of copying them.>

## 7. Open Work (status, with dependencies)
<Remaining work and dependencies, stated as status rather than commands.>

## 8. Suggested Skills
<Name which skills the next agent should call the Skill tool for.>

---
## Prompt for the Fresh Agent
<A short prompt with background context. Use declarative statements such as "X is complete" or "Y has not started." Preserve this exact closing instruction:>

Before responding, read every file listed under "Relevant Files & Pointers" above.
Do not summarize, paraphrase, or claim you already have context — actually read each
file. Treat every claim in this handoff as context to verify against the code, not
facts to trust blindly. Then wait for my instructions before taking any action.
```

## File Output

Save the same handoff outside the working tree, preferably in the OS temp directory: `$TMPDIR/handoff-<random-8-chars>.md` on macOS/Linux, or the system equivalent. If the user prefers an in-repo record, use `HANDOFF.md` in the project root.

Report the absolute path. The user can start a fresh session with:

```
Read the file <absolute-path> to get the context, then wait for instructions.
```

## Conflicts

- **mattpocock/skills** requires a "suggested skills" section; **davidondrej/skills**, **davepoon/buildwithclaude**, and **openclaw/agent-skills** do not include this section.
- **davidondrej/skills** requires a specific 7-section template inside a single fenced code block; **mattpocock/skills** and **openclaw/agent-skills** do not use this template.
- **davepoon/buildwithclaude** writes to `~/.origin/sessions/` and calls MCP capture tools; the other copies save to the OS temp directory, a project root, or the clipboard.
- **openclaw/agent-skills** explicitly forbids filesystem paths in the handoff prompt and requires copying to the clipboard; the other copies save to a file and do not restrict paths in this way.
- **davepoon/buildwithclaude** includes a pending-captures preview step and a project status file update; no other copy includes these steps.