Resume work from previous handoff sessions stored in .planning/handoffs/
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add jellydn/my-ai-tools --skill pickup --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pickup?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jellydn-pickup-my-ai-tools)More formats (shields.io, HTML) on the badges page.
---
name: pickup
description: "Resume work from previous handoff sessions stored in .planning/handoffs/"
license: MIT
compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi
hint: Use when resuming work from a previous handoff session
user-invocable: true
disable-model-invocation: true
metadata:
audience: all
workflow: workflow
---
# Pickup Handoff
Resumes work from previous handoff sessions which are stored in `.planning/handoffs/`.
## Usage
`/pickup [HANDOFF_FILE]`
If no handoff file is specified, will show available handoffs and prompt for selection.
## Process
1. Find available handoffs in `.planning/handoffs/`
2. Read the selected handoff file
3. Present the handoff summary to the user
4. Ask the user to confirm they want to continue
5. If confirmed, proceed with the next step described in the handoff
## Available Handoffs
To see available handoffs:
```bash
ls -la .planning/handoffs/
```
Handoffs are named in format: `[YYYY-MM-DD]-[slug].md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
