Session Handoff
Package in-progress work — state, decisions, open questions — so a new agent or session can continue without re-deriving it.
Before & after
Same prompt, same agent — the only difference is the skill.
Handing off work to someone else is important for team continuity. You'll want to make sure they understand what you've done, what's still in progress, and what decisions you made along the way. Writing down your progress and any blockers is helpful. You should also share any relevant context—like what the customer asked for, what you tried, and why you made certain choices. It's good to have a conversation with the person taking it over so they can ask questions. The goal is to avoid any surprises when they start working on it.
WORK HANDOFF PACKAGE STATUS SUMMARY • Task: Feature X (due 2026-08-15) • Completed: 60% (backend logic done; UI incomplete) • Blockers: API endpoint spec changed 2026-07-29; frontend dev paused • Handoff to: teammate name, timezone UTC+1 DELIVERABLES CHECKLIST ✓ PR #347: backend logic + tests (code review passed) ✓ Spike doc: API changes breakdown (3 endpoints affected) ✗ UI component: 40% done (branch: feature/ui-work) ✗ Integration tests: blocked on API stability CONTEXT & DECISIONS DECISION 1: Use caching layer for API responses → Why: 2.3s latency before; 200ms after cache (90% improvement) → Risk: cache invalidation edge case (documented in code comments) DECISION 2: Split into 2 smaller PRs instead of 1 large → Why: easier review; independent deploy possible → Impact: teammate can land backend solo if UI slips NEXT STEPS (Priority order) 1. Wait for API v3.2 release (ETA 2026-08-02) 2. Update frontend schema; re-run integration test suite 3. Build UI in 2 sprints: form input (3 days), validation UI (2 days) 4. Code review + deploy together in 1 batch QUESTIONS TO DISCUSS • Is API v3.2 release timeline still 2026-08-02? • Should we include validation error UX in scope, or defer to v2?
About this skill
name: skills-handoff description: Use when Structured Claude skill that gives Claude a repeatable workflow for skills handoff.
Skills Handoff
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Skills Handoff workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the skills-handoff skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Skills Handoff; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: skills-handoff
description: Use this skill when one Claude agent or session needs to hand off in-progress work to another with full context preserved.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Skills Handoff
Packages in-progress work — state, decisions, and open questions — into a structured handoff so a new agent or session can continue without re-deriving context.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.