pi/dot-pi/agent/skills/handoff/SKILL.md
Write a path-free, clipboard-ready handoff prompt that lets another agent investigate, discuss, or pick up a specific task.
npx skillsauth add nathankoerschner/dotfiles handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write a clipboard-ready prompt for another agent to investigate, discuss, or work on a specific task.
Use when the user asks for handoff <task>, "write a handoff", "delegate this",
or wants a prompt for another agent.
The prompt must:
Use this shape by default:
I want to discuss and possibly work on: <short task title>
Context:
- <portable repo/product context>
- <what triggered this task>
- <known current state, branch/issue/PR names or URLs if relevant>
- <important constraints and ownership boundaries>
Before doing any implementation:
- Find the right repository from the current directory, a parent directory, or the usual workspace.
- Read the local agent/repo instructions.
- Inspect the relevant code, docs, tests, recent commits, and linked issue/PR state.
- Decide whether this task is still real, whether the proposed direction is a good idea, and whether a smaller/better fix exists.
- Call out stale assumptions, hidden risks, and anything that should stop the work.
Task:
- <what to investigate or implement if the review supports it>
- <expected behavior or decision criteria>
- <non-goals>
Validation:
- <focused tests/checks/live proof expected>
- <what evidence should be included>
- <what is explicitly not required>
Output:
- Start with your review findings and recommendation.
- Then give the proposed plan or patch summary.
- If you edit code, keep changes scoped and report exact proof run.
- Do not push, merge, close issues/PRs, label, or post public comments unless explicitly told.
On macOS:
pbcopy < /tmp/handoff-prompt.txt
Use a temp file or pipe. Avoid inline shell quoting for prompts containing
backticks, $, quotes, or user text.
If pbcopy is unavailable, use the obvious platform clipboard tool (wl-copy,
xclip, clip.exe) or print the prompt and say clipboard copy was unavailable.
development
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to simplify, refactor lightly, clean up, or improve recently modified code without behavior changes.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
development
Run a Pi-based structured code review as a closeout check on local, branch, PR, or commit changes before commit or ship.
development
Deep, rigorous multi-model code review for PRs, branches, diffs, commits, or pre-merge checks. Use this when the user explicitly asks for a deep review, thorough review, rigorous review, pre-merge check, PR review, branch review, or wants maximum confidence. Do not use for quick/casual reviews; use quick-review instead. Treat AI output as a first draft: run independent Pi subagents on Claude Opus, GPT-5.5 extra-high reasoning, and Gemini; validate and synthesize severity-ranked findings before fixes.