Create a curated session summary for continuation. Use when the user asks to "hand off" or "create a handoff".
From mxnpx claudepluginhub maxwolf-01/agents --plugin mxThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Create a detailed handoff summary of the conversation for continuing work in a new session.
A handoff requires a purpose — what the next agent should do. If no purpose is clear, ask the user before proceeding.
The handoff file includes an <analysis> section (written to the file, not chat; EVERYTHING handoff specific goes into the file; the entire analysis goes ONLY into the file - do not summarize in chat beforehand) where you:
The handoff should include:
Create a descriptive slug using keywords separated by dashes, lowercase. More detail is better.
Good examples:
workflow-design-handoff-pickup-commands-wikilinksgemini-pdf-extraction-prompt-testing-latex-handlingstripe-webhook-eu-withdrawal-edge-casesBad examples (too vague):
gemini-integrationstripe-fix# <Readable Summary>
<analysis>
[Thought process, ensuring all points are covered]
</analysis>
<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]
- **Changes made**: [Summary]
- **Code snippet**:
```language
[Code]
[Solved problems and ongoing troubleshooting]
[Tasks requested but not done]
[What was being worked on before handoff]
[Required next step aligned with purpose]
Task/Knowledge:
External docs:
Key code files:
path/to/file.py — why this file matterspath/to/other.py — related contextBias toward MUST READ. You have context that shaped your thinking — the next agent doesn't. When in doubt, mark it MUST READ.
</plan> ```Write the handoff to: agent/handoffs/YYYY-MM-DD-<slug>.md
Then give the user the command to continue from there:
/mx:task agent/handoffs/YYYY-MM-DD-<slug>.md