skills.rest
ak110
ak110COMMUNITY
Explore all skills by this author →
Website𝕏@ak11GitHub

export-for-resume

Generate a resume-<topic>.md handover file with decisions, open items, and progress.

Updated Nov 12, 2017
Search Tags:#summarization#documentation#markdown#resume#conversation#handover#session-transfer
One-click install
npx skills add https://github.com/ak110/dotfiles --skill export-for-resume
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: export-for-resume
Source: https://github.com/ak110/dotfiles/tree/main/plugins/agent-toolkit/skills/export-for-resume
Command: npx skills add https://github.com/ak110/dotfiles --skill export-for-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This feature produces a concise, handover-ready markdown file that captures decisions, open items, and current progress from a session, enabling seamless continuation in a new Claude Code context.

Core Features & Use Cases

  • Extract and organize decisions, open items, and progress into a single document.
  • Output a file named resume-<topic>.md at the repository root for easy handoff and versioning.
  • Use-case: when discussions diverge or end, create a handover document to brief the next session without losing context.

Quick Start

Generate a resume-<topic>.md at the repository root to summarize the session for handoff to a new Claude Code session.

Frequently Asked Questions about export-for-resume

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

FAQPage Schema
How do I create a handover document from a stalled Claude Code session?▼

A handover document captures decisions, open items, and progress from a session. Generate a markdown summary file at the repository root to brief the next session without losing context.

What's the best way to summarize conversation decisions and open items for a new session?▼

Summarizing conversation decisions and open items requires extracting session progress into a structured markdown file. This separates decisions, open items, and progress into clearly defined sections for durable handoff.

How do I transfer context when a development conversation diverges across projects?▼

Transferring context when conversations diverge requires generating a resume markdown file at the repository root. This captures current progress and open items, enabling seamless continuation in a new Claude Code session.

Does generating a session handover markdown modify my existing code?▼

Generating a session handover markdown does not modify code. It outputs a new file named resume-<topic>.md at the repository root, preserving your existing project files while recording session state.

Can I use markdown to document session handovers for cross-project continuation?▼

Markdown is the output format for session handovers. The generated resume-<topic>.md file uses clearly separated sections for decisions, open items, and progress, making it easy to version and hand off across projects.

What sections should a conversation handover summary include for session transfer?▼

A conversation handover summary should include separate sections for decisions, open items, and current progress. This structure ensures the next session understands what was agreed upon and what remains unresolved.

Related Skills

Explore More Content & Communication Skills→
special-place-administratorspecial-place-administrator

session-handoff

Summarize active work into a compact HANDOFF block for the next session.

Community
Intermediate
jstoobzjstoobz
2

relay

Generate a CONTEXT_FOR_NEXT_SESSION.md handoff document for Claude Code sessions.

Community
Basic
Delphine-LDelphine-L
17

obsidian

Create session notes and tasks in an Obsidian vault with bidirectional links.

Community
Intermediate
844196844196
8

handover-tomorrow

Creates a reusable summary of a conversation's goals, constraints, and history for future sessions.

Community
Intermediate