Task Handoff
Create a compact, verifiable continuation record without transferring hidden reasoning or unrelated private context.
Workflow
- Name the objective, repository or system boundary, intended recipient, and exact continuation point.
- Verify current branch, revision, worktree state, remote or PR state, validation, and external surface state when each claim is relevant and accessible.
- Separate completed work, partially completed work, proposed work, blocked work, and work not started.
- Record decisions with their status and evidence. Preserve unresolved questions and named decision owners.
- List changed files or artifacts, commands already run, observed results, known failures, and safe next checks.
- State authorized actions, actions requiring new approval, sensitive context that is deliberately omitted, and stopping conditions.
- Provide the smallest ordered next-step list that lets the recipient verify before acting.
Boundaries
- Do not describe local work as pushed, a PR as merged, a preview as deployed, or a deployment as live without current evidence.
- Do not include chain-of-thought, raw transcripts, credentials, personal data, or unrelated repository details.
- A handoff transfers context, not authority.
- Write a file or send the handoff externally only when that destination and action are authorized.
Output
Lead with the continuation point and next verification or authorized action.
Retain the objective, exact revision and working state, changed artifacts,
completed and in-progress work, decisions, validation, blockers, evidence
references and freshness, existing authorization, and stop conditions. Use one
compact record unless a fuller handoff is requested or needed. Reverify stale
evidence before dependent action; do not repeat work already proved current.
Read the original acceptance example when checking this behavior.
Example
Synthetic example; not an observed client result.
Input: A patch passed tests at revision A, but the receiving checkout is B.
Output: Preserve the patch and receipt at A. Compare B before relying on those tests; carry forward the unfinished work and existing authorization.
1---2name: handoff-work3description: "Prepares a continuation record when explicitly asked to hand off or resume work elsewhere; records exact state, unfinished work, evidence, and existing authority without transferring new permissions."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/handoff-work7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "explicit"11 provenance: "original"12 risk_class: "bounded-execution"13---1415# Task Handoff1617Create a compact, verifiable continuation record without transferring hidden reasoning or unrelated private context.1819## Workflow20211. Name the objective, repository or system boundary, intended recipient, and exact continuation point.222. Verify current branch, revision, worktree state, remote or PR state, validation, and external surface state when each claim is relevant and accessible.233. Separate completed work, partially completed work, proposed work, blocked work, and work not started.244. Record decisions with their status and evidence. Preserve unresolved questions and named decision owners.255. List changed files or artifacts, commands already run, observed results, known failures, and safe next checks.266. State authorized actions, actions requiring new approval, sensitive context that is deliberately omitted, and stopping conditions.277. Provide the smallest ordered next-step list that lets the recipient verify before acting.2829## Boundaries3031- Do not describe local work as pushed, a PR as merged, a preview as deployed, or a deployment as live without current evidence.32- Do not include chain-of-thought, raw transcripts, credentials, personal data, or unrelated repository details.33- A handoff transfers context, not authority.34- Write a file or send the handoff externally only when that destination and action are authorized.3536## Output3738Lead with the continuation point and next verification or authorized action.39Retain the objective, exact revision and working state, changed artifacts,40completed and in-progress work, decisions, validation, blockers, evidence41references and freshness, existing authorization, and stop conditions. Use one42compact record unless a fuller handoff is requested or needed. Reverify stale43evidence before dependent action; do not repeat work already proved current.4445Read [the original acceptance example](references/continuity-example.md) when checking this behavior.4647## Example4849Synthetic example; not an observed client result.5051Input: A patch passed tests at revision A, but the receiving checkout is B.5253Output: Preserve the patch and receipt at A. Compare B before relying on those tests; carry forward the unfinished work and existing authorization.