Individual skill
handing-off-work
Hands off unfinished work with a closed-loop briefing of state, changed conditions, remaining scope, authority limits, and open evidence. Use when AI-agent, reviewer, verifier, releaser, or resumed-thread work transfers to a new owner. Do not use when the same owner continues uninterrupted with full context.
skills/handing-off-work/SKILL.md
Source commit e44af0e5811e11a3601625cf657d257915689deb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 33
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-safety Repository topic
- coding-agents Repository topic
- configuration-management Repository topic
- developer-tools Repository topic
- prompt-engineering Repository topic
- software-engineering Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Handing Off Work
## Overview
A handoff transfers responsibility, not just context. The next person or agent has to know what changed, what is left, what they are allowed to do, and when to stop.
## Decision contract
- **Claim checked:** the receiving owner can resume without the chat history -- the last finished action, changed conditions, remaining scope, authority limits, open evidence, and stop conditions are all stated -- and the owner has restated scope, authority, proof owed, and when to stop before acting.
- **Artifact observed:** the change-record path, current phase, mode, the done/changed/assumed/open state, and the authority limits -> a `turnover.md` with the resume point, what changed, what remains, the next decision gate, and the incoming owner's confirmation.
- **Decision affected:** block -- whether the receiving owner may resume, or must hold and re-question first.
- **Failure class:** open-loop-handoff (state only implied, or the owner acts before confirming scope and stop conditions).
- **Next action:** make the incoming owner restate scope, authority, and stop conditions first; escalate when credentials, production data, or release authority are involved.
