Skill

handoff

Generate a structured session handoff document for seamless context transfer to a fresh session. Use when ending a session, switching tasks, or context is getting full.

Install

npx claudepluginhub artmin96/forge-studio --plugin context-engine

Tool Access

This skill is limited to using the following tools:

ReadWriteBashGlobGrep

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Instructions

Parse the topic from $ARGUMENTS. If no argument is provided, default to session.

Gather context by running these commands:

git diff --name-only to get changed files
git log --oneline -5 to get recent commits
git status --short to see uncommitted work

Create the handoffs directory if it doesn't exist:

mkdir -p .claude/handoffs

Generate the handoff document at .claude/handoffs/{YYYY-MM-DD}-{topic}.md using today's date and the topic. Use the Write tool.

The document MUST follow this exact structure:

# Handoff: {topic}
Date: {YYYY-MM-DD}

## Done
- {bullet points of completed work with file paths}

## In Progress
- {what's partially done, current state}

## Blocked
- {blockers or unknowns, or "None" if clear}

## Decisions
- {key decisions made and WHY — rationale matters for future sessions}

## Files Changed
- `{path}` — {one-line summary}

## Next Steps
1. {prioritized list of what to do next}

## Gotchas
- {anything the next session should watch out for}

Keep the document under 200 tokens. Be terse. Use short bullet points. File paths are more useful than prose. This is a reference document, not a narrative.

Confirm by outputting: "Handoff saved to .claude/handoffs/{filename}. Start a new session and run /resume to pick up where you left off."

Session Handoff

Generate a compact handoff document for seamless context transfer to a new session.

Instructions

Parse the topic from $ARGUMENTS. If no argument is provided, default to session.
Gather context by running these commands:
- git diff --name-only to get changed files
- git log --oneline -5 to get recent commits
- git status --short to see uncommitted work
Create the handoffs directory if it doesn't exist:
```
mkdir -p .claude/handoffs
```

Generate the handoff document at .claude/handoffs/{YYYY-MM-DD}-{topic}.md using today's date and the topic. Use the Write tool.

The document MUST follow this exact structure:

# Handoff: {topic}
Date: {YYYY-MM-DD}

## Done
- {bullet points of completed work with file paths}

## In Progress
- {what's partially done, current state}

## Blocked
- {blockers or unknowns, or "None" if clear}

## Decisions
- {key decisions made and WHY — rationale matters for future sessions}

## Files Changed
- `{path}` — {one-line summary}

## Next Steps
1. {prioritized list of what to do next}

## Gotchas
- {anything the next session should watch out for}

Keep the document under 200 tokens. Be terse. Use short bullet points. File paths are more useful than prose. This is a reference document, not a narrative.
Confirm by outputting: "Handoff saved to .claude/handoffs/{filename}. Start a new session and run /resume to pick up where you left off."