---
id: gh-paseo-handoff
name: "paseo-handoff"
url: https://skills.yangsir.net/skill/gh-paseo-handoff
author: getpaseo
domain: ai-agent-orchestration-collaboration
tags: ["multi-agent-systems", "agent-orchestration", "workflow-automation", "task-management"]
install_count: 4800
rating: 4.40 (120 reviews)
github: https://github.com/getpaseo/paseo/tree/main/skills/paseo-handoff
---

# paseo-handoff

> 此技能允许将当前任务及其完整上下文无缝移交给另一个全新的 AI 智能体。它通过生成一份结构化的、自包含的简报，确保接收智能体即使从零开始也能迅速理解任务背景、已尝试方案、决策和约束，从而避免信息丢失，提高多智能体协作效率。特别适用于需要跨智能体接力完成复杂工作流的场景。

**Stats**: 4,800 installs · 4.4/5 (120 reviews)

## Before / After 对比

### 智能体任务交接效率提升

**Before**:

在没有这个技能之前，用户在切换或引入新智能体时，需要手动整理和传递大量上下文信息，容易遗漏关键细节，导致新智能体重复工作或理解偏差，耗费大量时间进行沟通和校正。

**After**:

该 Skill 自动生成包含所有必要信息的结构化简报，确保新智能体能立即投入工作，大幅减少手动整理和沟通时间，提高任务交接的准确性和效率。

| Metric | Before | After | Change |
|---|---|---|---|
| 上下文交接时间 | 60分钟 | 5分钟 | -92% |

## Readme

# Handoff Skill

Transfer the current task — context, decisions, failed attempts, constraints — to a fresh agent. The receiving agent starts with **zero context**, so the handoff prompt must be a self-contained briefing.

**User's arguments:** $ARGUMENTS

## Prerequisites

Read the **paseo** skill. Before choosing a provider, read `~/.paseo/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the receiving agent until you have read it.

## Parsing arguments

1. **Provider** — explicit user request first; otherwise resolve from `impl` preference (or `ui` if the task is styling-only).
2. **Worktree** — "in a worktree" / "worktree" → create a worktree via Paseo with a short branch name derived from the task, based on the current branch.
3. **Task description** — anything else the user said.

## The handoff prompt

The receiving agent has zero context. Include:

```
## Task
[Imperative description.]

## Context
[Why this task exists, required context.]

## Relevant files
- `path/to/file.ts` — [what it is and why it matters]

## Current state
[What's done, what works, what doesn't.]

## What was tried
- [Approach] — [why it failed or was abandoned]

## Decisions
- [Decision — rationale]

## Acceptance criteria
- [ ] [Criterion]

## Constraints
- [Must-not / must-preserve]
```

**Preserve task semantics.** Investigate-only → "DO NOT edit files." Fix → "implement the fix." Refactor → "refactor, not rewrite." Carry the user's exact intent.

## Launch

Create the agent via Paseo with a `[Handoff] <task>` title, the briefing as initial prompt, `detached: true`, and cwd set to the worktree path if `--worktree`. Leave `notifyOnFinish` omitted unless the user explicitly wants no callback.

Handoff agents are siblings/root agents, not your subagents. They must survive you being archived and must not appear in your subagent track.

Don't wait by default — the user decides whether to follow along or move on. Tell them the agent ID and how to follow along (the paseo skill explains).


---
*Source: https://skills.yangsir.net/skill/gh-paseo-handoff*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-paseo-handoff/markdown*