skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-session-handoff

Writes session handoff documents recording verified evidence, changes, blockers, and next steps.

Updated Jul 29, 2026
Search Tags:#documentation#markdown#agent workflow#workflow continuity#session handoff#evidence tracking
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-session-handoff-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-session-handoff
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-session-handoff
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-session-handoff-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working across multiple AI or developer sessions, context is lost between sessions and the next session cannot resume from chat history alone. This Skill creates a durable handoff document so the next session resumes from files, not conversation. ## Core Features & Use Cases - Structured Handoff File: Creates or updates docs/harness/session-handoff.md with required sections covering verified evidence, changes, blockers, decisions, next steps, and commands. - Evidence-Based Recording: Enforces exact commands and outputs rather than summaries, and requires blockers to be recorded with exact causes. - Safe Write Behavior: Shows the proposed content for approval before writing when the file is missing or structurally different. - Use Case: At the end of a coding session, record which checks passed, which files changed and why, what remains broken, and the single next action so a future session can continue without re-discovery. ## Quick Start Ask the agent to update the session handoff with everything verified, changed, and blocked in this session.

Frequently Asked Questions about harness-session-handoff

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

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

Write a session handoff document at docs/harness/session-handoff.md containing verified evidence, changes made, blockers, decisions, the next best step, and useful commands. The next session reads this file to resume without relying on chat history.

What should a session handoff document include?▼

It should include six sections: Verified Now with exact commands and outputs, Changed This Session with files and reasons, Broken Or Unverified items, Decisions Made with reasons, one concrete Next Best Step, and Commands for startup, validation, and recovery.

Where is the handoff file stored?▼

The handoff is stored at docs/harness/session-handoff.md in the project repository. If the file does not exist, the Skill proposes creating it and asks for approval before writing.

Does the handoff skill write files without confirmation?▼

No. When the target file is missing or structurally different from the expected format, the Skill shows the proposed handoff content first and asks for approval before writing anything.

Why record exact commands instead of summaries in a handoff?▼

Exact commands and outputs let the next session re-run and verify claims independently. Summaries alone cannot be validated, so the Skill requires concrete evidence for anything marked as verified.

Related Skills

Explore More Software Engineering Skills→
yknothingyknothing
1

verification-before-completion

Verify completion claims with fresh evidence and generate a verification-record.

Community
Advanced
shenxingyshenxingy
8

pickup

Load the latest `.claude/handoff-*.md` file and resume ordered next steps.

Community
Basic
minhtri2710minhtri2710

semantic-memory

Store and retrieve persistent learnings with metadata across software sessions.

Community
Basic
laicluselaicluse
4

naming-is-hard

Applies naming and wording doctrine to code symbols, branches, commits, PRs, and UI copy.

Official
Intermediate