القائمة
Compact the current conversation into a handoff document for another agent to pick up.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when executing implementation plans with independent tasks in the current session
Convert Claude's persisted memory into a structured high-level outline and save it to the project Obsidian vault. Use to archive and organize accumulated session knowledge as a navigable vault note.
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Set up and operate an LLM-maintained personal knowledge base wiki. Use when building a persistent, compounding knowledge base from source documents -- articles, papers, notes, transcripts, or any source material.
| name | handoff |
| version | 2.0 |
| category | superpowers |
| execution_speed | medium |
| token_efficiency | medium |
| triggers | ["handoff document","next session","compact conversation","transfer work"] |
| cache_key | handoff-2.0 |
| dependencies | [] |
| disable-model-invocation | true |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
