okhp3-session-handoff

Creates dated Markdown continuation records for work paused across sessions, machines, or agent hosts.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-session-handoff-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-session-handoff
Source: https://github.com/OKHP3/telling-forward/tree/main/.agents/skills/okhp3-session-handoff
Command: npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-session-handoff-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When work pauses, gets blocked, or moves between machines or AI agent hosts, chat memory disappears and context is lost. This Skill produces a durable, self-contained handoff record so the next session can resume without guessing what happened or why. ## Core Features & Use Cases - Structured Continuation Records: Writes a dated Markdown file capturing objective, status, changed files, reasoning, evidence tiers (confirmed, inferred, proposed, unknown), validation results, limitations, and the exact next action. - Safe Failure Behavior: Returns BLOCKED instead of guessing when the handoff destination is not identified, and never claims another copy received or applied the handoff without direct inspection. - History-Preserving Updates: Adds dated addenda when new evidence changes prior conclusions, preserving the earlier record rather than rewriting it. - Use Case: After a long debugging or writing session, ask for a handoff before switching machines; the next agent reads the record and resumes from the exact next action with full context. ## Quick Start Use the okhp3-session-handoff skill to write a continuation record for this work to my approved handoff folder.

Frequently Asked Questions about okhp3-session-handoff

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

FAQPage Schema
How do I hand off work between AI agent sessions?▼

Provide the project root, handoff destination, objective, and current work inventory. The skill writes a dated Markdown record with changed files, reasoning, checks run, and the exact next action so the next session resumes without chat memory.

What should a session handoff document include?▼

A handoff record should include source host and date, objective and status, changed files, decision reasoning, confirmed versus inferred conclusions, checks run and not run, known limitations, and the exact next action with files needed to resume.

What happens if no handoff destination is specified?▼

The skill returns BLOCKED rather than guessing a path. It names the missing destination choice and does not claim that another copy received or applied the handoff unless that destination was directly inspected.

How are handoff records updated when evidence changes?▼

When new evidence contradicts an existing record, the skill adds a dated addendum to the same handoff if it remains the natural continuity record. It preserves the earlier conclusion and explains why it changed instead of rewriting history.

What are the limitations of a session handoff record?▼

The record does not provide account access, publication, or source preservation, and it cannot guarantee another copy applied the handoff. It is out of scope for anything beyond portable continuation records across sessions, machines, or agent hosts.