From Harness
Compact the current conversation into a handoff document so the next agent or session can continue without reading the history. Use at the end of any phase, or when the user is wrapping up and wants a clean starting point for the next session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/harness:handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A single markdown document that gives a fresh agent everything it needs to pick up exactly where this session left off — without reading this conversation.
A single markdown document that gives a fresh agent everything it needs to pick up exactly where this session left off — without reading this conversation.
Reference, don't duplicate. Do not re-paste content that already exists in .harness/ files or other artifacts — link to them instead.
Identify:
.harness/ file written or updated this session (path + one-line summary of what changed).harness/adr/Save to the OS temp directory — never to the repo:
$TMPDIR → /tmp → %TEMP% (Windows)handoff-[YYYY-MM-DD-HHmm].md# Handoff — [YYYY-MM-DD HH:mm]
## Context
One paragraph: what this project is, where it sits in the development lifecycle, and what this session accomplished.
## What was done this session
- [artifact or action] — [one-line summary]
## Current state
- **Phase**: ideation / product / engineering / implementation / qa / docs
- **Features done**: [list, or "none yet"]
- **Features in progress**: [list, or "none"]
- **Blockers**: [list, or "none"]
## Key decisions made in conversation
Only decisions NOT already in .harness/adr/. Omit ephemeral reasoning ("chose X because it was faster today") — only capture things that would surprise a future agent.
## Artifacts to read first
In priority order for the next agent:
1. [path] — [why it matters]
2. ...
## Suggested next skill
/[skill-name] — [one sentence on what it will do and why now]
## Notes for next agent
Anything surprising, any implicit constraints, or any context that doesn't emerge from reading the artifacts alone.
Omit any section that has nothing to say. Redact secrets, API keys, and PII before writing.
Output the full absolute path to the handoff file. If the user wants to start a new session, they can paste the file contents as the first message.
npx claudepluginhub rubenglez/harness --plugin harnessGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.