handoff

Generate structured handoff documents with prompt, instructions, file references, and Git context.

24|59|Updated Aug 28, 2015
One-click install
npx skills add https://github.com/mParticle/mparticle-web-sdk --skill handoff-mparticle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/mParticle/mparticle-web-sdk/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/mParticle/mparticle-web-sdk --skill handoff-mparticle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured handoff documents to transfer session context between AI sessions, ensuring continuity and traceability.

Core Features & Use Cases

  • Context preservation: Captures decisions, constraints, blockers, and rationale to accompany the handoff.
  • Automated document creation: Produces handoff-<task>-<YYYYMMDD>.md with a prompt, instructions, ranked file references, Git context, and working directory.
  • Companion workflow: Integrates with /kickstart to restore context in a new session for seamless handovers.

Quick Start

Run /handoff <goal> to generate a handoff document for transferring context to a new session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer AI session context to a new session?

To transfer AI session context, you can generate a structured handoff document that preserves decisions, constraints, and ranked file references for the new session. This ensures continuity and traceability across your workflow.

What is the best way to preserve decisions and rationale for a post-handoff AI session?

Preserving decisions and rationale for a post-handoff AI session requires capturing context in a standardized document format. This document includes the original prompt, instructions, Git context, and working directory to ensure reproducibility.

How do I create a handoff document with Git context for an AI workflow?

You create a handoff document with Git context by running a command that outputs a structured markdown file. This file automatically records your working directory, Git context, and ranked file references to enable seamless session transfers.

Can I restore context in a new AI session after generating a handoff document?

Yes, you can restore context in a new AI session by using a companion workflow designed to read the generated handoff document. This integration allows the new session to seamlessly pick up the preserved task context.

Does the handoff document format include working directory and file references?

Yes, the handoff document format explicitly includes your working directory, Git context, and ranked file references. It also contains the prompt and instructions needed to accurately reconstruct your previous session state.

When do I need a structured handoff document for session transfers?

You need a structured handoff document for session transfers when your task requires context retention, decision tracing, and post-handoff reproducibility. It prevents knowledge loss when moving complex work between different AI sessions.