Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From agent-meta
Resumes parked coding sessions from handoff documents: locates in CLAUDE.md or .parkinglot/, summarizes next steps, validates git branches/files, offers update or fresh start options.
npx claudepluginhub technicalpickles/pickled-claude-plugins --plugin agent-metaHow this skill is triggered — by the user, by Claude, or both
Slash command
/agent-meta:unparkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Resume work from a parked handoff document.
Saves current work session context including git state, tasks, decisions, relevant files, and next steps to a markdown file for later /unpark resumption.
Manages context handoffs between AI coding sessions. Detects HANDOFF.md files on startup, trigger words like 'handoff' or 'resume', and suggests transfers at milestones or session ends.
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session.
Share bugs, ideas, or general feedback.
Resume work from a parked handoff document.
Check parking locations in order:
CLAUDE.md → ## Handoffs or ## Parking → Location:~/.claude/CLAUDE.md → same lookup.parkinglot/ in project rootIf multiple handoffs exist, list them and ask which to resume:
Found parked sessions:
(A) jwt-authentication.md - Parked 2026-01-30
(B) fix-login-bug.md - Parked 2026-01-29
(C) Other location
Read the handoff document and present a summary:
Resuming: [Topic]
Parked: [Date]
Branch: [branch]
Current state: [Brief summary]
Next steps:
1. [Step 1]
2. [Step 2]
Check that the handoff is still valid:
If valid:
Validation passed. Ready to continue with: [first next step]
Proceed?
(A) Yes, continue
(B) Review the full handoff first
(C) Adjust the plan
If stale or invalid:
Validation found issues:
- [Issue 1]
- [Issue 2]
Options:
(A) Update handoff and try again - I'll revise based on current state
(B) Start fresh - discard this handoff
(C) Continue anyway - I understand the context has changed
If option A: Update the handoff file with current findings, then recommend running /unpark again.
Handoff docs may contain a Session: field with the session ID that parked the work. This enables tracing work across park/unpark cycles. If present, the session chain looks like:
Session A (parked) -> handoff.md -> Session B (unparked) -> parked again -> ...
Session tracking tools (if available) can use this to link sessions together.