handover
starsforks
How to install handover?
soul-brews-studio/arra-oracle-skills-cli/handover
$npx -y skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill handoverTransfer work to another Oracle — forward + wake + tell in one command. Use when user says "handover", "hand over", "transfer to", "pass to", or wants to delegate work to another oracle.
SKILL.md
| 1 | # /handover — Transfer Work to Another Oracle |
| 2 | |
| 3 | Forward + Wake + Tell in one command. You're done, they continue. |
| 4 | |
| 5 | ## Usage |
| 6 | |
| 7 | ``` |
| 8 | /handover neo "continue #117, PR ready for review" |
| 9 | /handover pulse "alpha released, triage 9 open issues" |
| 10 | ``` |
| 11 | |
| 12 | ## Steps |
| 13 | |
| 14 | ### 1. Write Handoff (like /forward) |
| 15 | |
| 16 | ```bash |
| 17 | PSI=$(readlink -f ψ 2>/dev/null || echo "ψ") |
| 18 | mkdir -p "$PSI/inbox/handoff" |
| 19 | ``` |
| 20 | |
| 21 | Write to: `$PSI/inbox/handoff/YYYY-MM-DD_HH-MM_handover-to-<oracle>.md` |
| 22 | |
| 23 | ```markdown |
| 24 | # Handover to <oracle-name> |
| 25 | |
| 26 | **Date**: YYYY-MM-DD HH:MM |
| 27 | **From**: [current Oracle] |
| 28 | **To**: <oracle-name> |
| 29 | **Instruction**: <instruction> |
| 30 | |
| 31 | ## Context |
| 32 | - [What we were working on] |
| 33 | - [Key decisions made] |
| 34 | |
| 35 | ## Pending |
| 36 | - [ ] [Items to continue] |
| 37 | |
| 38 | ## Key Files |
| 39 | - [Important files] |
| 40 | ``` |
| 41 | |
| 42 | ### 2. Wake Target Oracle |
| 43 | |
| 44 | ```bash |
| 45 | maw wake <oracle-name> |
| 46 | ``` |
| 47 | |
| 48 | Wait 3 seconds for startup. |
| 49 | |
| 50 | ### 3. Send Instruction + Handoff Path |
| 51 | |
| 52 | ```bash |
| 53 | maw hey <oracle-name> "Handover from [self]: <instruction>. Handoff file: $PSI/inbox/handoff/... — read it with /recap" |
| 54 | ``` |
| 55 | |
| 56 | ### 4. Output |
| 57 | |
| 58 | ``` |
| 59 | Handed over to <oracle-name>: |
| 60 | Handoff: ψ/inbox/handoff/... |
| 61 | Instruction: "<instruction>" |
| 62 | → <oracle-name> is awake and has context |
| 63 | ``` |
| 64 | |
| 65 | ## Rules |
| 66 | |
| 67 | - Always write handoff BEFORE waking target |
| 68 | - Include handoff file path in the message so target can /recap |
| 69 | - Do NOT enter plan mode (unlike /forward) — handover is immediate |
| 70 | - Do NOT ask for confirmation — user already decided to hand over |
| 71 | |
| 72 | ARGUMENTS: $ARGUMENTS |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
