handoff

Capture session progress, decisions, risks, and next steps into a structured handoff note.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/supertyrelle/pelley --skill handoff-supertyrelle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/supertyrelle/pelley/tree/main/skills/handoff
Command: npx skills add https://github.com/supertyrelle/pelley --skill handoff-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents loss of context when a long coding session ends, helping the next session resume with the same understanding of goals, decisions, risks, and open work.

Core Features & Use Cases

  • State capture: Reviews backlog status, recent git activity, and current working state so nothing important is forgotten.
  • Decision logging: Records key choices, rejected alternatives, and the reasoning behind them for future continuity.
  • Risk and dependency tracking: Flags unfinished work, blockers, and unresolved questions that could slow the next session.
  • Use case: Ideal before a break, after a major implementation chunk, or whenever a fresh session is recommended and you need a clean transition.

Quick Start

Use the handoff skill to summarize the current session, capture the important decisions and risks, and write a structured transition note for the next session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve context when ending a long coding session?

To preserve coding session context, capture git history, uncommitted changes, and backlog status into a structured handoff note. This records decisions, rejected alternatives, and open questions so the next session resumes without losing continuity or progress.

What is the best way to track risks and blockers before a development session transition?

Tracking risks before a session transition involves flagging unfinished work, unresolved questions, and dependencies in a persistent handoff note. This ensures blockers are documented alongside recent git activity so the next development session understands what needs immediate attention.

How do I document decisions and rejected alternatives for my AI coding workflow?

Documenting decisions for AI coding workflows requires logging key choices and their reasoning into a structured transition note during session handoffs. This captures rejected alternatives and backlog status so future sessions maintain the same understanding of project goals.

When do I need to create a session handoff note for my development workstream?

You need a session handoff note before planned breaks, after major implementation chunks, or when changing workstreams. It assembles git history, uncommitted changes, and next steps into a persistent record so the next session resumes with full context of open work.

Can I use a handoff note to capture uncommitted changes and git history?

Yes, a handoff note captures uncommitted changes and recent git history alongside backlog status and open questions. This assembles the current working state into a persistent transition record so the next session resumes with full visibility of the codebase state.

Does this session transition approach work for long-running development sessions?

Yes, this session transition approach is designed for long-running development sessions where progress, decisions, and open questions must be preserved. It structures backlog status, git activity, and risks into a persistent note to prevent context loss across breaks.