session-handoff
Session Handoff generates a structured document that captures current project state, completed and in-progress work, key decisions made, and specific context needed to resume development in a subsequent session. Use this skill when ending a work session and planning to continue later, or when transitioning work to a different time block.
git clone --depth 1 https://github.com/rohitg00/pro-workflow /tmp/session-handoff && cp -r /tmp/session-handoff/skills/session-handoff ~/.claude/skills/session-handoffSKILL.md
# Session Handoff Different from wrap-up. Wrap-up is a checklist for *you*. Handoff is a document written for the *next session*. ## Trigger Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly. ## Workflow 1. Gather current state from git. 2. List completed, in-progress, and pending work. 3. Note key decisions made and their reasoning. 4. Capture any learnings from this session. 5. Generate a resume command for the next session. ## Commands ```bash git status git diff --stat git log --oneline -5 git branch --show-current ``` ## Output ```markdown # Session Handoff — [date] [time] ## Status - **Branch**: feature/xyz - **Commits this session**: 3 - **Uncommitted changes**: 2 files modified - **Tests**: passing / failing / not run ## What's Done - [completed task 1] - [completed task 2] ## What's In Progress - [current task with context on where you stopped] - [file:line that needs attention next] ## What's Pending - [next task that hasn't been started] - [blocked items with reason] ## Key Decisions Made - [decision 1 and why] - [decision 2 and why] ## Learnings Captured - [Category] Rule (from this session) ## Files Touched - `path/to/file1.ts` — [what changed] - `path/to/file2.ts` — [what changed] ## Gotchas for Next Session - [thing that tripped you up] - [non-obvious behavior discovered] ## Resume Command > Continue working on [branch]. [1-2 sentence context]. Next step: [specific action]. ``` ## Guardrails - Write for the reader (next session), not the writer. - Include specific file paths and line numbers where relevant. - The resume command should be copy-pasteable into the next session. - Keep it factual — describe changes functionally, don't infer motivation.
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
Analyze session token usage and cost patterns. Identify expensive operations and recommend optimizations. Use to understand and reduce session costs.
Specialized debugging agent. Use when facing hard bugs, test failures, or runtime errors that need systematic investigation.
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
Analyze permission denial patterns and generate optimized alwaysAllow/alwaysDeny rules. Use when permission prompts slow down workflow.
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.