---
name: handoffs-581a687b6cb9
description: "Create handoff plans for continuing work across sessions"
license: MIT
compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi
hint: Use when ending a session and want to continue work later with full context
user-invocable: true
metadata:
  audience: all
  workflow: workflow
---

# Session Handoff Plan

Creates a detailed handoff plan of the conversation for continuing the work in a new session.

The user specified purpose:

<purpose>$ARGUMENTS</purpose>

You are creating a summary specifically so that it can be continued by another agent. For this to work you MUST have a purpose. If no specified purpose was provided in the `<purpose>...</purpose>` tag you must STOP IMMEDIATELY and ask the user what the purpose is.

Do not continue before asking for the purpose as you will otherwise not understand the instructions and do not assume a purpose!

## Goal

Create a detailed summary of the conversation so far, paying close attention to the user's explicit purpose for the next steps.
This handoff plan should be thorough in capturing technical details, code patterns, and architectural decisions that will be essential for continuing development work without losing context.

## Process

Before providing the final handoff, produce a concise evidence-based summary for the user. Do not expose private chain-of-thought or `<analysis>` tags. Include decisions, current state, blockers, and the exact next action instead of a chronological transcript or full code dumps.

1. Identify the user's explicit purpose and the current work state.
2. Verify important paths, branch/status, recent command results, and unresolved blockers.
3. Capture only decision-relevant file names, symbols, short snippets, and links.
4. Mark uncertain or stale information explicitly.


Your plan should include the following sections:

1. **Primary Request and Intent**: Capture all of the user's explicit requests and intents in detail
2. **Key Technical Concepts**: List all important technical concepts, technologies, and frameworks discussed.
3. **Files and Code Sections**: Enumerate specific files and code sections examined, modified, or created. Pay special attention to the most recent messages and include full code snippets where applicable and include a summary of why this file read or edit is important.
4. **Problem Solving**: Document problems solved and any ongoing troubleshooting efforts.
5. **Pending Tasks**: Outline any pending tasks that you have explicitly been asked to work on.
6. **Current Work**: Describe in detail precisely what was being worked on immediately before this handoff request, paying special attention to the most recent messages from both user and assistant. Include file names and code snippets where applicable.
7. **Next Step**: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's explicit requests, and the task you were working on immediately before this handoff request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests without confirming with the user first. Include this section only if there is an actionable next step.

Additionally create a "slug" for this handoff. The "slug" is how we will refer to it later in a few places. Examples:

- current-user-api-handler
- implement-auth
- fix-issue-42

Together with the slug create a "Readable Summary". Examples:

- Implement Current User API Handler
- Implement Authentication
- Fix Issue #42

## Output Structure

The handoff file should contain the structured summary below. Do not include private chain-of-thought or a chronological transcript.

```markdown
# Session Handoff Plan

## 1. Primary Request and Intent

[Detailed description of all user requests and intents]

## 2. Key Technical Concepts

- [Concept 1]
- [Concept 2]
- [...]

## 3. Files and Code Sections

### [File Name 1]

- **Why important**: [Summary of why this file is important]
- **Changes made**: [Summary of the changes made to this file, if any]
- **Code snippet**:

\`\`\`language
[Important Code Snippet]
\`\`\`

### [File Name 2]

- **Code snippet**:

\`\`\`language
[Important Code Snippet]
\`\`\`

[...]

## 4. Problem Solving

[Description of solved problems and ongoing troubleshooting]

## 5. Pending Tasks

- [Task 1 that you have been explicitly asked to work on]
- [Task 2 that you have been explicitly asked to work on]
- [...]

## 6. Current Work

[Detailed description of what was being worked on immediately before this handoff, including file names and code snippets]

## 7. Next Step

[Next step to take, directly aligned with user's explicit handoff purpose. Only include if there is an actionable next step.]
```

## Final Step

After providing your analysis and summary:

1. Ensure the `.planning/handoffs/` directory exists (create it if needed)
2. Write the handoff summary to a markdown file at `.planning/handoffs/[timestamp]-[slug].md` where [timestamp] is the current date in format YYYY-MM-DD and the slug is what we defined before
3. Read the handoff file back and verify it contains the purpose, current state, verification, blockers, and next action.
4. Tell the user about this file and that they can use `/pickup $1` to continue where $1 is the filename


---
Source attribution: jellydn
Original project: https://github.com/jellydn/my-ai-tools/blob/920edf11fefa249af3bce8750625d4ca92ed8364/skills/handoffs/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice

The MIT License (MIT)

Copyright (c) 2026 Dung Huynh Duc

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Mega AI Hub resource metadata

Creator / publisher: jellydn
Original project: https://github.com/jellydn/my-ai-tools/blob/920edf11fefa249af3bce8750625d4ca92ed8364/skills/handoffs/SKILL.md
Attribution basis: Source repository record

Fields of work: Product Management, Project & Program Management, Sales
Roles: Customer Success Manager, Project Manager, Technical Product Manager
Specialties: API, Word Documents, Frontend
Tools: Tool not specified
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 234e41bbced2ad3c10c841a56509a41001e44bdb35585463338027f8b9f77a8c