paseo-handoff

Transfers the current task with full context to a fresh Paseo agent.

Updated Nov 25, 2024
One-click install
npx skills add https://github.com/cbrostrom/dotfiles --skill paseo-handoff-cbrostrom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paseo-handoff
Source: https://github.com/cbrostrom/dotfiles/tree/main/stow/agents/.agents/skills/paseo-handoff
Command: npx skills add https://github.com/cbrostrom/dotfiles --skill paseo-handoff-cbrostrom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task outgrows the current conversation or needs a different agent profile, starting over means losing context. This Skill packages the current task — decisions, failed attempts, constraints, and relevant files — into a self-contained briefing so a fresh agent can continue with zero prior context. ## Core Features & Use Cases - Self-contained briefing generation: Builds a structured handoff prompt covering task, context, relevant files, current state, failed attempts, decisions, acceptance criteria, and constraints. - Profile-aware agent selection: Reads configured Paseo profiles via list_profiles and picks the receiving agent whose notes best match the work. - Workspace isolation support: Optionally creates a worktree-isolated workspace with a short branch name derived from the task. - Use Case: You have been debugging a failing build and want a specialist agent to take over. Say "hand this off to the backend profile in a worktree" and the Skill launches a new agent with a complete briefing, preserving your exact intent. ## Quick Start Say "hand off this task to another agent" and optionally name a profile or request worktree isolation.

Frequently Asked Questions about paseo-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off a task to another AI agent without losing context?▼

Invoke the handoff with a phrase like "hand this off" and the Skill builds a structured briefing covering the task, context, relevant files, current state, failed attempts, decisions, and acceptance criteria. The receiving agent starts with zero context, so the briefing must be fully self-contained.

How does the handoff choose which agent profile receives the task?▼

It calls list_profiles first and reads each profile's notes, then selects the profile whose notes best match the work unless you name one explicitly. If no profile fits, it falls back to Paseo's provider discovery.

Can I hand off a task into an isolated git worktree?▼

Yes. Saying "in a worktree" or "worktree" triggers workspace creation with isolation set to worktree, using a short branch name derived from the task. The new agent then works in that isolated workspace.

Does the handoff wait for the receiving agent to finish?▼

No. The Skill launches the agent and returns immediately without polling. The new agent stays in your subagent track until you manually detach it through the Paseo interface.

What are the limitations of agent-to-agent task handoff?▼

The receiving agent gets only what the briefing contains, so omitted context is permanently lost. Detach is a manual user gesture, not something the Skill can perform, and investigate-only versus fix intent must be stated explicitly to be preserved.