skills.rest
qte77
qte77COMMUNITY
Explore all skills by this author →
WebsiteGitHub

handing-off-session

Generate structured Markdown session handoff notes with decisions, tasks, and blockers.

2|1|Updated Feb 22, 2026
Search Tags:#workflow#markdown#blockers#handoff#notes#session#context-switching
One-click install
npx skills add https://github.com/qte77/claude-code-plugins --skill handing-off-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handing-off-session
Source: https://github.com/qte77/claude-code-plugins/tree/main/plugins/cc-meta/skills/handing-off-session
Command: npx skills add https://github.com/qte77/claude-code-plugins --skill handing-off-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured session handoff notes to preserve context across work sessions.

Core Features & Use Cases

  • Create a concise, standardized handoff document capturing decisions, open tasks, blockers, and next steps.
  • Integrate with existing workflows by outputting a Markdown file to a known path and including essential metadata.
  • Use case: at project handoff between developers or when resuming after a break, the handoff note guides the next session.

Quick Start

Write a session handoff note to the default path with the latest session summary.

Frequently Asked Questions about handing-off-session

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

FAQPage Schema
How do I generate session handoff notes for preserving context across work breaks?▼

Generate session handoff notes by creating a structured Markdown file to preserve context across work sessions. It outputs a document with sections for What Was Done, What's Pending, Key Decisions, Modified Files, and Blockers to ensure continuity.

What's the best way to write structured markdown handoff notes for developer project transitions?▼

Writing structured markdown handoff notes is best handled by generating a standardized file capturing decisions, open tasks, and blockers. The output guides the next session at project handoff between developers or when resuming after a break.

Can I specify a custom file path for my session handoff notes instead of using the default directory?▼

Session handoff notes output to a deterministic default path of .claude/handoffs/YYYY-MM-DD-<short-description>.md. The metadata does not detail custom path configuration, so the file is written to this known location for workflow integration.

When do I need to create context-switching handoff notes during a development workflow?▼

Create context-switching handoff notes at the end of a session, during project context switches, or after breaks. This process preserves session continuity by documenting modified files and pending work before stepping away.

What key sections should be included in markdown handoff notes to track blockers and pending tasks?▼

Markdown handoff notes should include sections for What Was Done, What's Pending, Key Decisions, Modified Files, and Blockers. This structure captures essential metadata and open tasks to guide the next work session.

Related Skills

Explore More Software Engineering Skills→
vddgmbhvddgmbh

create-scratch

Create scratch files in .agents/scratches/ with unique three-word IDs and YAML frontmatter.

Official
Basic
specvitalspecvital
1

handover

Generate a markdown handoff summary with context, decisions, and pending tasks.

Official
Basic
TruCol270TruCol270
1

gsd-thread

Create, list, and resume file-based context threads under .planning/threads.

Community
Intermediate
bhaumikmaanbhaumikmaan
3

session-handoff

Generate structured session handoff notes with fixed templates and token budgets.

Community
Advanced