mcpField
P
paseo-handoff

paseo-handoff

github.com/getpaseoAgent workflows22.3k4.9k installsUpdated today
Repository

About paseo-handoff

paseo-handoff is an agent skill for transferring a task to a fresh Paseo agent with no prior context. It guides the creation of a self-contained briefing, profile selection, and workspace placement while preserving the user's intent.

Key features

  1. 01Prepare a self-contained task briefing
  2. 02Select an agent profile using its notes
  3. 03Create a dedicated workspace when requested
  4. 04Preserve task constraints and intent

Use cases

  1. 01Hand off an investigation to a fresh agent
  2. 02Delegate a fix while retaining task requirements
  3. 03Move a task into a separate worktree

MCP support

The skill uses Paseo agent and workspace operations, including profile discovery and agent creation, which can be invoked through Paseo's MCP tools.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/getpaseo/paseo --skill paseo-handoff

After installing, type/paseo-handoffin Claude Code to confirm it loaded.

Details

From the project 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. 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.

Comments

Markdown supported