/paseo-handoff
Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.
Claude Code
$ npx -y skills add getpaseo/paseo --skill paseo-handoff --agent claude-code
Codex
$ npx skills add getpaseo/paseo --skill paseo-handoff -a codex -y
Cursor
$ npx skills add getpaseo/paseo --skill paseo-handoff -a cursor -y
Gemini CLI
$ npx skills add getpaseo/paseo --skill paseo-handoff -a gemini-cli -y
GitHub Copilot
$ npx skills add getpaseo/paseo --skill paseo-handoff -a github-copilot -y
OpenCode
$ npx skills add getpaseo/paseo --skill paseo-handoff -a opencode -y
Windsurf
$ npx skills add getpaseo/paseo --skill paseo-handoff -a windsurf -y
SKILL.md
paseo-handoff.SKILL.mdname: paseo-handoff
description: Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.
user-invocable: true
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.
Use the user's request and current conversation as input, including any arguments supplied with the skill invocation.
Prerequisites
Read the **paseo** skill. Call `list_profiles` before choosing the receiving agent. Do not create it until you have read the configured profiles and their `notes`.
Parsing arguments
1. **Agent profile** — explicit profile name first; otherwise choose the profile whose `notes` best match the work. Materialize it into `create_agent` as described by the **paseo** skill. If no profile fits, use Paseo's provider discovery fallback. 2. **Isolation** — "in a worktree" / "worktree" → create a workspace with `isolation: "worktree"`, using a short branch name derived from the task. 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
Prepare the handoff in a dedicated workspace:
1. Select the current workspace or call `create_workspace` with the requested isolation. 2. Call `create_agent` with a `[Handoff] <task>` title, the briefing as initial prompt, and the selected `workspaceId` when explicit placement is needed. 3. Return the agent and workspace to the user, explaining that it remains in your subagent track until they detach it manually.
Do not encode independence as a create mode and do not invoke CLI or wire-level detach operations. Detach is a user gesture in the subagents track.
Do not wait or poll for the agent to finish.
Read more
name: paseo-handoff description: Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent. user-invocable: true
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.
Use the user's request and current conversation as input, including any arguments supplied with the skill invocation.
Prerequisites
Read the **paseo** skill. Call `list_profiles` before choosing the receiving agent. Do not create it until you have read the configured profiles and their `notes`.
Parsing arguments
1. **Agent profile** — explicit profile name first; otherwise choose the profile whose `notes` best match the work. Materialize it into `create_agent` as described by the **paseo** skill. If no profile fits, use Paseo's provider discovery fallback. 2. **Isolation** — "in a worktree" / "worktree" → create a workspace with `isolation: "worktree"`, using a short branch name derived from the task. 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
Prepare the handoff in a dedicated workspace:
1. Select the current workspace or call `create_workspace` with the requested isolation. 2. Call `create_agent` with a `[Handoff] <task>` title, the briefing as initial prompt, and the selected `workspaceId` when explicit placement is needed. 3. Return the agent and workspace to the user, explaining that it remains in your subagent track until they detach it manually.
Do not encode independence as a create mode and do not invoke CLI or wire-level detach operations. Detach is a user gesture in the subagents track.
Do not wait or poll for the agent to finish.
Other skills on paseo.
More skills from other plugins.
10x
Personalized audit that teaches the advanced Paradev (formerly Superset) features the user isn't using yet (automations, parallel…
ao-actions
Direct actions on one Orchestrator session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's…
capabilities
Your capability catalog — read this at boot. Lists the temporal date-range skills and the external integrations (reached via the…
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Questions about paseo-handoff.
- Which coding agents can use paseo-handoff?
- paseo-handoff installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

