| name | handoff |
| type | Skill |
| title | Session Handoff and Context Continuity |
| description | Create a session handoff and resumption checkpoint before you clear chat history or start a new session. Inspect workspace state, write HANDOFF.md, and create a prompt to start the next session.
Use when:
- You want to run /clear or start a new session.
- You want to save current progress, decisions, and uncommitted code.
- You want a prompt to resume work in a new conversation.
Do not use when:
- You make normal git commits without ending the session.
- You write brief status messages. |
| tags | ["handoff","session-management","context-continuity","checkpoint","developer-workflow","okf"] |
| status | verified |
| generated | 2026-08-06T02:30:00.000Z |
| personas | ["software-engineer","technical-writer","ai-agent"] |
Session Handoff
The handoff skill saves context before you reset a session (such as /clear or starting a new chat).
This skill uses two mechanisms to keep context:
- Workspace Memory: A structured
HANDOFF.md file written in the root directory of the workspace. It records code state, decisions, failed attempts, and backlog ideas.
- Resumption Prompt: A prompt that the user copies into the new session to start work immediately.
The Handoff Workflow
When you start a handoff, do these five steps in order:
graph TD
A[1. Inspect State] --> B[2. Collect Context]
B --> C[3. Write HANDOFF.md]
C --> D[4. Create Resumption Prompt]
D --> E[5. Show Output to User]
Step 1: Inspect the Workspace State
Do not rely on conversational memory alone. Run commands to inspect the real workspace state:
- Check Git and File Status:
git status -s
git diff --stat
git branch --show-current
- Identify In-Progress Work:
- Find modified files, untracked files, and temporary files.
- Record exact file paths and line numbers.
- Record Test Status:
- If tests fail, record the exact error messages and failing test names.
- Review Conversation History:
- Identify the main goal and current milestone.
- Record technical decisions and rejected alternatives.
- Record ideas or future improvements discussed with the user.
Step 2: Collect the Six Context Elements
Collect and structure information into six elements:
| Element | Description | Purpose |
|---|
| 1. Goal and Milestone | Main task and current sub-task | Gives the new agent immediate context. |
| 2. Completed Work | Finished code and passing tests | Prevents repeated work. |
|
