360 Secure SkillHub
360 安全技能中心

paseo-handoff

读取 Paseo profiles 后选择接收 agent,整理包含任务、上下文、文件、状态、尝试、决策、验收和约束的交接简报,并在指定或新建 workspace 中创建子 agent;不等待完成,detach 由用户操作。

getpaseo
热度 58.91
最近更新 2026-10-19 02:26:21
分类:协作依赖:MCP 服务应用场景:任务管理 / 工作流 / 模板

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add getpaseo/paseo/paseo-handoff
Metadata
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.

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.