Menü
Capture current session state to a handoff file. Use before /clear, when context is getting full, or when ending a session mid-task.
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
| name | handoff |
| description | Capture current session state to a handoff file. Use before /clear, when context is getting full, or when ending a session mid-task. |
| disable-model-invocation | true |
| argument-hint | [label] |
| effort | low |
Capture the current session state into a timestamped handoff file.
$ARGUMENTS is optional — pass a short label to identify the handoff (e.g. scoring-engine-wip).
Write a concise handoff file that lets a fresh session resume exactly where this one left off — without needing to re-read the conversation history.
git status and git diff HEAD --stat to see what files changed this session.claude/specs/ for the most recently modified spec (the active work item).claude/reviews/ for any open review reports.claude/handoffs/YYYY-MM-DD-HH-MM.md using this structure:# Handoff: <label or inferred task name>
Date: <timestamp>
## Current task
<One sentence: what are we building or fixing?>
## Pipeline position
<Which skill was running or is next: /0_spec / /1_implement / /2_review / /3_fix / /4_test>
## Active files
- Spec: `.claude/specs/<name>.md` (if applicable)
- Review: `.claude/reviews/<name>-review.md` (if applicable)
- Key source files: <list only files actively being worked on>
## Decisions made this session
<Bullet list of non-obvious choices made — things not visible from reading the code>
## Open questions
<Unresolved issues or things to verify before continuing. Write "None" if clean.>
## Next step
<Exact action to take when resuming — specific enough to execute without rereading the conversation>
/clear after confirming the handoff looks correct, then /continue in the new session to restore contextCreate well-structured atomic commits with conventional commit messages. Use when ready to commit working changes.
Write a feature spec from requirements in .claude/input/. Use when starting a new feature, before implementation begins.
Orchestrate the full spec → implement → review → fix → commit pipeline. Use when shipping a complete feature end-to-end.
Break a concept document, draft, or product brief into independent PRDs that each feed into /ship. Use when input contains multiple features or a big-picture vision.
Ship decomposed PRDs in parallel. Analyzes file conflicts, groups into batches, runs /ship in isolated worktrees, merges results. Use after /decompose.
Implement a feature from a spec file in .claude/specs/. Use after a spec is written and approved.