Handoff
Compact the current conversation into a handoff document for another agent to pick up. Use when requested by a user, when the current thread would be best carried out in a fresh thread, or when the context window is getting too full.
Install
$ agentstack add skill-bambam955-skills-handoff ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bambam955-skills-handoff) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Handoff
Write a handoff document summarizing the current conversation so a fresh agent can continue the work. Closely follow [the template](./templates/handoff.template.md) for document structure.
Workflow
- Ask for clarity, if needed, on any of the following:
- Goal for the new thread (default: implement the plan)
- Specific context/decisions to emphasize (default: max of 5 major points)
- Relevant files to link in the doc (default: max of 5 heavily modified files)
- Compact the current conversation into a concise, actionable summary document. Follow [this template](./templates/handoff.template.md).
- Ensure all clarified points are included.
- If any code changes/other work was WIP at time of handoff, it should be included/referenced.
- Include any config/setup details relevant to the task at hand.
- Save the document to
PLAN.md(or user-set path if--plan-file=was passed).
Guidelines
- Never duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Always reference those artifacts by path/URL instead.
- Never over-summarize/over-generalize to the point that key context from the current thread is lost.
- Always tread
goals-for-next-threadas a description of what the next thread will focus on. Tailor the handoff doc accordingly.
Output
A single PLAN.md file in the current workspace. The filepath can be overridden if the user passes --plan-file= as an argument.
Gotchas
- Do not include absolute file paths, in case a user wants to give the plan to someone else
- Leave out any sensitive information (API keys, passwords, personal identifiers)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bambam955
- Source: bambam955/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.