harness-clean-handoff

Generates session handoff reports with evidence, verification results, and git status.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-clean-handoff-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-clean-handoff
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-clean-handoff
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-clean-handoff-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending an agent session without a structured handoff forces the next session to re-derive trust from zero: which work was verified, which metrics failed, and what to do next are all lost. This Skill standardizes the exit process so evidence, blockers, and next steps are captured before a session closes. ## Core Features & Use Cases - Exit Checklist: Identifies the active task from feature lists, specs, or session todos, then collects actual gate-report evidence rather than prose claims. - Structured Handoff Report: Produces a session-handoff document with fixed sections covering verified metrics, changes, broken or unverified items, decisions, next steps, and reproducible commands. - Refine Phase Fallback: When no scheduler ran and the primary agent is spec-lead, runs the Refine phase and presents its proposal in the report without writing any ledger or standards files. - Use Case: Before closing a long coding session, invoke the handoff to record the gate report metrics verbatim, list red and unavailable metrics, and leave the next session a reproducible command trail. ## Quick Start Run the clean handoff before ending this session and produce a handoff report with the latest verification evidence and git status.

Frequently Asked Questions about harness-clean-handoff

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

FAQPage Schema
How do I hand off an AI agent session without losing progress?

Run the clean handoff before closing the session. It identifies the active task, collects gate-report evidence, updates progress notes, and writes a session-handoff document with verified metrics, open issues, and the next best step.

What should a session handoff report include?

Include sections for Verified Now with the metric table verbatim, Changed This Session, Broken Or Unverified covering red and unavailable metrics, Decisions Made, Next Best Step, and Commands so the next session can reproduce results.

Does the handoff skill mark tasks as passing or blocked?

No. The handoff only suggests status transitions to PREVC and never writes passing, blocked, or any lifecycle status. PREVC owns all lifecycle decisions; the handoff returns a report only.

What happens when verification was skipped during handoff?

Skipped verification must be recorded with a reason, and any stale or missing gate report is listed under Broken Or Unverified. The handoff never claims completion when verification failed or was skipped without justification.

When does the Refine phase fallback trigger?

It triggers only when no scheduler ran during the session and the primary agent is spec-lead, since only spec-lead holds task allow permission. The fallback presents a proposal in the report without writing the ledger or standards files.