session-handoff
Capture current session state and generate a handoff prompt for seamless continuation in a new session. Use when context window is filling up, before ending a long session, or when explicitly requested.
What this skill does
# Session Handoff Generate a complete handoff package that allows a new session to resume work seamlessly. ## When to Use - Context window approaching limit (agent or user notices slowdown/truncation) - Before intentionally ending a productive session - User requests handoff explicitly - Complex task needs to span multiple sessions ## Handoff Process ### Step 0: Check Token Budget Read `.claude/memory/.memory-config.md` for token budget (if exists): - `economy`: Session summary ~200-400 tokens (brief, 2-3 sentences) - `light`: Session summary ~400-700 tokens (concise, 3-5 sentences) - `standard`: Session summary ~600-1000 tokens (default, 5-8 sentences) - `detailed`: Session summary ~900-1500 tokens (comprehensive, 8-12 sentences) If no config exists, use `standard` budget. ### Step 1: Sync Memory First Before generating handoff, ensure memory is current: - Update active-context.md with current state - Add any new decisions to decisions/ - Update progress.md with completed/in-progress items - Create session summary in sessions/ **Session file format:** `sessions/YYYY-MM-DD-HHMM.md` or `sessions/YYYY-MM-DD-topic.md` > **Note:** Include timestamp (HHMM) to avoid overwriting previous same-day sessions. The topic suffix is preferred when a clear topic exists. ```markdown # Session: [date] ## Summary Brief summary of what was accomplished. - economy: 2-3 sentences - light: 3-5 sentences - standard: 5-8 sentences (default) - detailed: 8-12 sentences with comprehensive context ## Work Completed - [Item 1] - [Item 2] ## Decisions Made - ADR-NNN: [title] (if applicable) ## Context for Next Session - [Key context point] ## Open Questions - [Question if any] --- *Session duration: ~[time]* ``` ### Step 2: Gather Handoff Context Collect from conversation and memory: - **Original goal:** What the user asked for - **Current task:** What we're actively working on - **Progress:** What's been completed this session - **Remaining work:** What still needs to be done - **Key decisions:** Decisions made this session (reference ADRs if created) - **Blockers/questions:** Unresolved issues - **Critical files:** Files being actively modified - **Recent errors:** Any errors we're debugging ### Step 3: Generate Handoff Prompt Output a fenced code block the user can copy/paste: ~~~markdown ## Handoff Prompt (copy everything below this line) ``` I'm continuing work on [project-name] from a previous session. ## Original Goal [What the user originally asked for] ## Session Summary [2-3 sentence summary of what was accomplished] ## Current State - **Active task:** [What we were working on when session ended] - **Files in progress:** [List of files being modified] - **Last action:** [What the agent just did or was about to do] ## Completed This Session - [Item 1] - [Item 2] ## Remaining Work - [ ] [Task 1 - next priority] - [ ] [Task 2] - [ ] [Task 3] ## Key Decisions Made - [Decision 1] (see ADR-NNN if applicable) - [Decision 2] ## Open Questions/Blockers - [Question or blocker if any] ## Context to Load Project memory is at: .claude/memory/ Key files to review: [list critical files] Please load the project memory and continue with [specific next task]. ``` ~~~ ### Step 4: Confirm Handoff Complete After outputting the prompt: > Session handoff complete. Memory has been synced. > > Copy the prompt above and paste it into a new session to continue. > > Key files updated: > - active-context.md (current state) > - progress.md (task status) > - sessions/[date].md (session summary)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.