Menü
Resume work from a parked handoff
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when investigating an agent-harness CLI's internals (Claude Code, codex, opencode, or similar): extracting the system prompt or tool descriptions, finding what code path produces a specific UI message, decoding minified function names or Rust symbols, understanding undocumented config keys, or otherwise spelunking a shipped binary (or its pinned source) to figure out how the tool actually behaves.
Use when about to lock in a non-trivial or hard-to-reverse decision, fire AskUserQuestion to offload a call, proceed on your own preferred option, or assert something is done / found / tested / fixed / "that's how it works" — especially when the basis is memory, the handoff, the first framing, or an unchecked assumption rather than something verified this session. Also invoked as /gut-check. Use even when you feel confident; confidence is the symptom, not the all-clear.
Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.
Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that's distinct from", "versus"), bolded terms followed by colons, or an embedded "X, Y, and Z" series. Composes with prose-clarity skills (concision) and voice skills (personality) rather than replacing them. Skip for source code and for casual one-line replies where formatting reads as overkill.
| name | unpark |
| description | Resume work from a parked handoff |
Resume work from a parked handoff document, or read a wrapped close-out record as reference.
Check parking locations in order:
CLAUDE.md -> ## Handoffs or ## Parking -> Location:~/.claude/CLAUDE.md -> same lookup.parkinglot/ in project rootIf multiple files exist, group them by mode and list:
Active handoffs:
(A) jwt-authentication.md - Parked 2026-05-06
(B) fix-login-bug.md - Parked 2026-05-04
Wrapped (reference only):
(C) sanitation-skill-fix-wrapped.md - Wrapped 2026-03-30
(D) confirm-dotfiles-work-role-wrapped.md - Wrapped 2026-04-12
(E) Other location
Detect group by filename suffix (-wrapped.md) and the file's first heading (Parked: vs Wrapped:). Filename and heading should agree; if they disagree, trust the heading and note the mismatch.
After the user picks a file, read it and check the first heading.
# Parked: -> continue with Continuation Flow below# Wrapped: -> switch to Reference Flow belowRead the handoff 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 unparking again.
For Wrapped: files. No validation runs by default. Present the file as a reference:
This is a close-out record, not a handoff. Showing it as reference.
Wrapped: [topic]
Date: [...]
Outcome: [first paragraph from Outcome section]
Options:
(A) Read the full record
(B) Start fresh work building on this (invokes brainstorming with this doc as context)
(C) Treat as continuation anyway (runs full validation despite the heading)
Option (A): print the file contents as a reference, no further action.
Option (B): invoke superpowers:brainstorming and pass the wrapped doc's path as starting context.
Option (C): rare escape hatch. Treat the file as if it were a continuation and run the validate step from the Continuation Flow. Useful if the user wrapped something prematurely.
Both Parked: and Wrapped: files include a Session: field. Session tracking tools can use this to link work across sessions:
Session A (parked) -> handoff.md -> Session B (unparked) -> parked again -> ...
Session A (wrapped) -> wrapped.md -> [end of chain, unless treated as continuation]
Parked: file with old shape (Resume Prompt at bottom): Works fine. The validation flow does not depend on section order.