- Claude Code
- Agent
- Beginner
- Claude Code
- Published
Session Handoff Note for a Fresh Claude Code Session
Writes a verified handoff file covering changes, decisions, open issues and next steps so a new Claude Code session can continue without re-reading the whole history.
You get: Working code with an explanation
Ready to use: no blanks to fill in.
The prompt
mkdir -p .agents/skills/session-handoff-note-for-a-fresh-claude-code-session && curl -sL "https://prompts-gpt.com/prompts/session-handoff-note-for-a-fresh-claude-code-session/raw" -o .agents/skills/session-handoff-note-for-a-fresh-claude-code-session/SKILL.md---
name: session-handoff-note-for-a-fresh-claude-code-session
description: "Writes a verified handoff file covering changes, decisions, open issues and next steps so a new Claude Code session can continue without re-reading the whole history."
---
# Session Handoff Note for a Fresh Claude Code Session
Writes a verified handoff file covering changes, decisions, open issues and next steps so a new Claude Code session can continue without re-reading the whole history.
## Prompt
```
You are closing out this Claude Code session. Ask me one short question: which file should the handoff go in (default HANDOFF.md at the repo root). Then write it so a fresh session with no memory can continue immediately. Rules: 1) Verify with git status and git diff --stat rather than memory, and list only changes that really exist, with file paths. 2) Record decisions with the reason and the alternatives rejected, so they are not reopened. 3) Separate facts you confirmed from guesses, and include failing tests or errors with the exact command and message. 4) Next steps must be ordered, specific and runnable, and the first one should be doable in five minutes. 5) Keep it under 80 lines and do not paste large diffs. Output the file with sections Goal, State of the Work, Changes Made, Decisions and Why, Open Issues, Next Steps, and Commands to Resume, then a two-line summary for me and any files you left uncommitted.
```
## Usage Notes
Use it at the end of a long session, before running /clear or closing the terminal. Start the next session by telling Claude Code to read the handoff file first.
You are closing out this Claude Code session. Ask me one short question: which file should the handoff go in (default HANDOFF.md at the repo root). Then write it so a fresh session with no memory can continue immediately. Rules: 1) Verify with git status and git diff --stat rather than memory, and list only changes that really exist, with file paths. 2) Record decisions with the reason and the alternatives rejected, so they are not reopened. 3) Separate facts you confirmed from guesses, and include failing tests or errors with the exact command and message. 4) Next steps must be ordered, specific and runnable, and the first one should be doable in five minutes. 5) Keep it under 80 lines and do not paste large diffs. Output the file with sections Goal, State of the Work, Changes Made, Decisions and Why, Open Issues, Next Steps, and Commands to Resume, then a two-line summary for me and any files you left uncommitted.Example output
Tips and common edits
Use it at the end of a long session, before running /clear or closing the terminal. Start the next session by telling Claude Code to read the handoff file first.
Questions about this prompt
More like this
More in Claude CodeTyped Phase Handoff Contracts and Validator for Multi-Agent Pipelines
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Conventional Commit and PR Description Writer Skill (SKILL.md)
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
Characterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.
Claude Code Behavior-Preserving Refactor with Characterization Tests and Staged Commits
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Claude Code Feature Implementation Plan and Build from a Ticket with Repo Convention Discovery
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Claude Code Hook Writer: Auto-Run Lint, Typecheck or Tests After Edits
Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.
Claude Code Plan-Then-Implement a Feature With Approval Checkpoints
Makes Claude Code explore the repo, write a step-by-step plan for your approval, then build the feature in small verified steps, stopping at each checkpoint for your go-ahead.
Claude Code Root-Cause Bug Investigation with Failing Test and Minimal Patch
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Coding Agent Task Brief with Guardrails, Test Plan, and Rollback Steps
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.