القائمة
Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full-lifecycle orchestration for comprehensive, no-compromise execution — roll-calls the right skills, fans out parallel/worktree agents, then closes the loop (verify, review, simplify, changelog, handoff, retro). Use when you want maximum effort, to go all-in, or to orchestrate a big task end-to-end.
Runs a short retrospective that PROPOSES edits to the user's Claude Code skills — capturing a newly-found gotcha, fixing a description that didn't auto-trigger, retiring a dead skill, or extracting a reusable pattern into a new skill. Improves the TOOLSET, not the session log. Use when the user signals satisfaction at the end of real work ("thanks", "thanks that worked", "that worked great", "nice", "perfect", "exactly what I needed"), or when they explicitly run /session-retro. Always proposes and waits for confirmation — never edits skills silently. In unattended runs (/orchestrate, overnight, or /session-retro --auto), writes proposals to ~/.claude/retro-proposals/ instead of blocking.
Deep task decomposition into parallel workstreams with self-contained agent prompts. Use when you want to review the execution plan before committing to it.
Generate a handoff note for clean session transitions — preserves context across /clear or new sessions. Use when ending a session, when context is getting high, or when the user says "hand off", "wrap up the session", or "save state for next time".
Inspect and clean stale branches across multiple repositories using the dotfiles git-hygiene + gh-bootstrap toolchain. Use when the user asks about branch state, stale local branches, or "no ref was fetched" errors.
Update a project CHANGELOG.md or equivalent session log with concise notes about completed changes, decisions, and known issues.
| name | handoff |
| description | Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps. |
Use when the user asks for a handoff, context note, session summary, or resume brief.
git status --short.~/.claude/operator-queue.md — see
"Operator-action queue" below for the block format and rules.git worktree list — remove worktrees this session created and no
longer needs (git worktree remove <path>).git branch --merged "$(git rev-parse --abbrev-ref origin/HEAD)" —
don't assume it's named main), excluding the default and current
branches.gh pr list — note each open PR's review + CI state in the
handoff's "Open issues" section.~/.claude/handoffs/YYYY-MM-DD-<project>-handoff.md —
the same directory the Claude /handoff skill uses, so either tool can
resume the other's session. Create the directory if needed. Never save it
inside the public repo.Use the same section names as the Claude /handoff skill so notes are
interchangeable across tools:
## Handoff — YYYY-MM-DD
### What we did
- ...
### Where we left off
- ...
### Key decisions made
- ...
### Open issues
- ...
### Next steps
- ...
### Context for next session
- ...
### Session continuity
- (optional) Resumable agent sessions: my Codex session id (`codex resume <id>`),
or an agy conversation id (`agy --conversation <id>`). Omit if none.
Keep it concise. Do not include secrets, private project details, tokens, or machine-specific paths unless the user explicitly asks and the destination is private.
Anything only the operator can do (rotate a token, click an approval, decide
on a purchase) goes to the durable queue at ~/.claude/operator-queue.md —
handoff prose gets buried by the next handoff; the queue does not. One item
per block:
## <stable-slug>
- added: YYYY-MM-DD
- project: <source project>
- deadline: YYYY-MM-DD
- action: <one line: what the operator must do>
The slug is stable (same action = same slug across sessions); deadline is
optional — omit the line if none. Append only if absent — match on the
slug, never re-add or duplicate an existing item. Remove an item's block
only when the action is actually done, not when it's merely mentioned
again.