handoff

Document session context into progress.md and generate a kick-off prompt.

13|4|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ggombee/code-forge --skill handoff-ggombee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ggombee/code-forge/tree/main/skills/handoff
Command: npx skills add https://github.com/ggombee/code-forge --skill handoff-ggombee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines session handoff by automatically documenting important context into 'progress.md' and providing a kick-off prompt, ensuring seamless continuation of tasks.

Core Features & Use Cases

  • Automated Session Documentation: Captures completed actions, pending tasks, and important decisions in 'progress.md'.
  • Customizable Prompt Generation: Creates a tailored kick-off prompt for the next session, based on the session's context.
  • Use Case: After a coding session, use the handoff skill to document the progress and generate a prompt to quickly resume the next session.

Quick Start

To perform a handoff, simply run '/handoff'.

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 handing off a coding session to another developer?

Session handoff automation captures completed actions, pending tasks, and decisions into 'progress.md'. It generates a kick-off prompt so the next session resumes with full contextual clarity.

What is the best way to automate session continuation for coding tasks?

Automating session continuation is handled by running '/handoff'. This user-initiated command documents session context and provides a tailored kick-off prompt for the next session.

How does automated contextual documentation work for session management?

Automated contextual documentation works by writing session progress into 'progress.md'. It requires user interaction to initiate the handoff and document the current state before ending the session.

Do I need any dependencies to use this session handoff automation?

No dependencies are required for this session handoff automation. It operates independently using scripts to document context into 'progress.md' and generate a kick-off prompt.

When should I not use automated session handoff for context preservation?

You should not use automated session handoff if your work requires no future continuation. This Skill relies on user interaction to initiate the process, making it unsuitable for fully autonomous background logging.