skills.rest
nikkogibler
nikkogiblerCOMMUNITY
Explore all skills by this author →
GitHub

handoff

Create date-stamped markdown handoff documents with decisions and next steps.

2|Updated May 1, 2026
Search Tags:#documentation#markdown#context#handoff#continuation#knowledge-transfer#session-summaries
One-click install
npx skills add https://github.com/nikkogibler/MarsFounderIO --skill handoff-nikkogibler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/nikkogibler/MarsFounderIO/tree/main/my-instructions/skills/handoff
Command: npx skills add https://github.com/nikkogibler/MarsFounderIO --skill handoff-nikkogibler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a date-stamped markdown handoff document that captures enough verified context for another agent to resume quickly and safely. Use when the user asks for a handoff, session summary, continuation brief, context file, or wants to save work state for another agent.

Core Features & Use Cases

  • Generates a structured handoff with verified context, decisions, and open items.
  • Supports various scenarios: session handoffs, continuation briefs, and context saving for future agents.
  • Adheres to standardized filename conventions and storage guidelines to ensure discoverability and consistency.

Quick Start

Run the handoff command to generate a dated session handoff next to the primary artifact.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a handoff document for transferring context to another agent?▼

To create a handoff document, generate a structured markdown file with sections for decisions, files touched, validation status, and next steps to preserve verified context for seamless continuation.

What is a session summary and when do I need one for collaborative workspaces?▼

A session summary is a date-stamped markdown document capturing verified context and open items, needed when saving work state for another agent to resume collaborative work safely.

Does the handoff process enforce specific filename conventions for context files?▼

Yes, the handoff process enforces date-stamped filenames and stores context files under chat_session_summaries when available, ensuring discoverability and consistency across collaborative workspaces.

What's the best way to save context for future agents working on markdown documentation?▼

The best way to save context is generating a continuation brief that captures verified decisions, touched files, and next steps in a standardized markdown file next to the primary artifact.

What sections should a continuation brief include for knowledge transfer?▼

A continuation brief should include sections for decisions, files touched, validation status, and next steps to ensure effective knowledge transfer and seamless continuation.

Related Skills

Explore More Content & Communication Skills→
fukukei23fukukei23

resume-session

Load recent handoff records and reconstruct active work state.

Community
Advanced
thrawn01thrawn01
11

handoff

Generate a structured handoff brief listing active tasks, touched files, and next steps.

Community
Intermediate
pinion05pinion05
3

daily-memory

Log daily work entries with timestamps into date-stamped markdown files.

Community
Basic
ArabelaTsoArabelaTso
142

session-handoff

Create structured markdown context summaries for continuing work across AI sessions.

Community
Basic