record-session-handoff

Records evidence-grounded task handoffs for continuation in later AI-agent sessions.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mtk177a/skills --skill record-session-handoff-mtk177a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: record-session-handoff
Source: https://github.com/mtk177a/skills/tree/main/skills/record-session-handoff
Command: npx skills add https://github.com/mtk177a/skills --skill record-session-handoff-mtk177a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When work must pause or move to a new AI-agent session, context is lost and the next session may fabricate missing state, overwrite unrelated notes, or treat stale authorization as current. This Skill produces a self-contained, evidence-grounded handoff so a blank-slate session can resume safely. ## Core Features & Use Cases - Evidence classification: Separates observed, reported, inferred, unknown, and conflicting claims, and tracks confirmed versus pending or superseded decisions. - Orthogonal state reporting: Assigns exactly one handoff state (Ready to resume, Needs confirmation, Blocked) and one persistence state (Written, Draft only, Not written). - Safe persistence rules: Writes only to an explicitly authorized destination, refuses to overwrite newer or different-task handoffs, strips secrets and private data, and never renews prior high-risk authorization. - Use Case: You are pausing a parser refactor mid-task. The Skill records the confirmed retry decision, the unverified test report, the uncommitted diff, and the next safe action with entry and stop conditions as a draft, since no storage destination was authorized. ## Quick Start Ask the agent to record a session handoff for the current task so a later session can resume it safely.

Frequently Asked Questions about record-session-handoff

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

FAQPage Schema
How do I preserve task state across AI agent sessions?▼

Ask the agent to record a session handoff before switching sessions. It captures the current goal, confirmed decisions, observed versus reported state, blockers, and the next safe action with entry and stop conditions, so the next session resumes without reconstructing the conversation.

What happens if no handoff storage destination exists?▼

The Skill returns the handoff as a draft with persistence state Draft only instead of inventing a notes path or filename. It never treats invocation itself as write authority; only an explicit user-supplied destination or authoritative existing convention permits writing.

Can a handoff overwrite an existing latest handoff file?▼

Only after confirming the existing artifact belongs to the same task and contains no newer or conflicting state. If that cannot be established, the Skill leaves it unchanged, reports Not written, and identifies the conflict rather than replacing unrelated content.

Does a recorded handoff renew authorization for risky actions?▼

No. A handoff records prior authorization only as historical evidence. Destructive, external, privileged, or high-risk actions require fresh revalidation of authority, target state, and recovery evidence in the next session before execution.

When should I not use a session handoff?▼

Do not use it for routine progress reports, change summaries, commit or PR drafting, release handoffs, durable policy or ADR updates, automatic session start or end behavior, or blindly executing an existing handoff without revalidating its state.