pickup

Claim the most recent open handoff and hydrate its full context.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill pickup-sanskarbasnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pickup
Source: https://github.com/sanskarbasnet/fstack/tree/main/pickup
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill pickup-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claim a handoff and hydrate full context in one command. It selects the most recent open handoff addressed to you (or by --id), marks it picked_up, and surfaces the parent intent, recent edits on referenced files, and related decisions.

Core Features & Use Cases

  • Single-command handoff hydration: claim the handoff and load its full context for immediate visibility.
  • Digest of work: prints the parent intent, recent edits on referenced files, and related decisions to keep teams aligned.
  • Safe handoff takeover: marks the handoff as picked_up and relies on subsequent /sync confirmation from the original author to preserve attribution.

Quick Start

Run /pickup to claim the most recent open handoff assigned to you and hydrate its full context.

Frequently Asked Questions about pickup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I claim a handoff and load the full context in one command?▼

You can claim a handoff and hydrate context by running /pickup, which selects the most recent open handoff addressed to you, marks it picked_up, and surfaces the parent intent, recent edits, and related decisions.

What information is included when I hydrate context for a handoff?▼

Hydrating context returns the full handoff details, the parent intent, recent edits on referenced files, and related decisions to keep your team aligned during the handoff takeover.

Can I claim a specific handoff by its ID instead of the most recent one?▼

Yes, you can claim a specific handoff by providing the --id parameter to select and hydrate that exact handoff instead of automatically claiming the most recent open one assigned to you.

How does handoff pickup preserve attribution between team members?▼

Handoff pickup preserves attribution by marking the handoff as picked_up in the brain, relying on the original author's subsequent /sync confirmation to validate your takeover of the task.

What's the best way to review recent edits and decisions before taking over a task?▼

Running /pickup is the best way to review recent edits and decisions, as it automatically surfaces a digest of recent edits on referenced files and related decisions when claiming the handoff.

Why does a handoff need to be marked as picked_up in the brain?▼

A handoff is marked as picked_up in the brain so the original author's next /sync confirms your takeover, ensuring safe handoff transition and accurate attribution across the team.