Menu
Compact the current conversation into a handoff document for another agent to pick up.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/youpele52/bigbud --skill handoffThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work.
Do not include a "suggested skills" section.
If any skills were actually used during the thread and that is relevant follow-up context, include a "Skills used in this thread" section that lists:
Omit that section entirely when no relevant skills were used.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
Return the document in exactly this XML block and nothing else:
<handoff_document> FULL_MARKDOWN_DOCUMENT_BODY </handoff_document>
Do not include commentary before or after the XML block.
Collects the details needed to create or update a bigbud automation and emits a machine-readable automation request block.
Guide structured, multi-session learning with persisted missions, lessons, and reference docs in a dedicated bigbud learning folder. Use when the user wants to learn something over time, start a learning project, build a course, or says "teach me over time" or "I want to learn X properly" — not for one-off explanations of code or quick answers.
Create well-formatted git commits with review and clear messages in the bigbud project. Use when the user asks to commit changes, write a commit message, review changes before committing, or asks about commit conventions.
Based on SOC occupation classification
