wrap-up

Generate a WRAP_UP.md session handoff file with decisions and pending work.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kikolator/claude-toolkit --skill wrap-up-kikolator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/Kikolator/claude-toolkit/tree/main/skills/wrap-up
Command: npx skills add https://github.com/Kikolator/claude-toolkit --skill wrap-up-kikolator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a WRAP_UP.md session handoff file at the project root lets you preserve context from a Claude Code session, capture decisions, pending work, and prompts to resume seamlessly.

Core Features & Use Cases

  • Generate WRAP_UP.md at the project root containing a structured session summary, decisions, pending tasks, touched files, and a ready-to-paste Claude Code resume prompt.
  • Guidance on whether to commit or ignore WRAP_UP.md, with a clear workflow for resuming work across sessions.
  • Provides a ready Resume Prompt format to kick off the next session without re-explaining context.
  • Supports partial requests by capturing relevant context and suggestions for the next steps.

Quick Start

Run the wrap-up skill to save your current session context to WRAP_UP.md in the project root.

Frequently Asked Questions about wrap-up

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save Claude Code session context for a future resume?

To save Claude Code session context, generate a WRAP_UP.md handoff file at your project root. This file captures decisions, pending tasks, touched files, and a ready-to-paste resume prompt to seamlessly continue work in a new session.

What is a session handoff file and when do I need one?

A session handoff file preserves context across Claude Code sessions when work spans multiple interactions. You need one to capture decisions, pending work, and file touchpoints so the next session starts without re-explaining the project state.

How do I resume a project in Claude Code without re-explaining the context?

Resume a project without re-explaining context by pasting the self-contained resume prompt generated inside the WRAP_UP.md file. This prompt kicks off the next Claude Code session with all prior decisions and pending tasks already loaded.

Should I commit the WRAP_UP.md file to git or add it to .gitignore?

You can either commit or ignore the WRAP_UP.md file based on your team workflow. The skill provides a recommended .gitignore rule to exclude it from version control if you prefer keeping session handoffs local.

Can I generate a session summary for an ongoing project with only partial work completed?

Yes, you can generate a session summary for ongoing projects with partial work. The handoff file captures relevant context, completed decisions, and suggestions for the next steps, even if the overall task is not fully finished.

What's the best way to document touched files and pending tasks before closing a Claude Code session?

The best way to document touched files and pending tasks is generating a WRAP_UP.md file at the project root. It provides a structured session template that records file touchpoints and pending work for seamless future handoffs.