handoff

Automates capture of in-session journey summaries in YAML and Markdown formats.

45|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill handoff-rakovi4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/rakovi4/continue-framework --skill handoff-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically captures and preserves journey summaries during work sessions, ensuring no valuable information is lost and providing a comprehensive record for future reference.

Core Features & Use Cases

  • Automated Journey Summary: Captures noteworthy moments in a work session automatically and upon request.
  • Idempotent and Lazy Creation: Skips recording if the information is already covered.
  • File Layout and Constraints: Follows a strict format to maintain consistency and organization.

Quick Start

Use the /handoff command to capture a journey summary at the end of a work session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I automate work session documentation to preserve conversation context?

Work session documentation is automated by capturing in-session journey summaries using YAML and Markdown. This preserves conversation context and continuity across tasks, ensuring no valuable information is lost during future reference.

How do I capture a journey summary at the end of a task?

You capture a journey summary by using the /handoff command at the end of a work session. This triggers an automated capture of noteworthy moments into a structured Markdown format.

Does generating journey summaries require knowledge of YAML syntax?

Generating journey summaries requires knowledge of YAML syntax and file naming conventions. This prerequisite ensures the automated context preservation follows strict file layout constraints for consistency.

Will the conversation capture process record duplicate information?

The conversation capture process uses idempotent and lazy creation to skip recording if the information is already covered. This prevents duplicate entries and maintains a clean work session documentation record.

What is the best way to maintain context continuity across multiple conversations?

The best way to maintain context continuity across multiple conversations is by capturing journey summaries in YAML and Markdown. This provides a comprehensive, structured record for maintaining context across tasks and stories.

When should I not use automated journey summary capture?

Automated journey summary capture should not be used if you lack knowledge of file naming conventions and YAML syntax. The strict file layout constraints require this technical understanding to maintain organization and consistency.