Transfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.
Installs into .claude/skills of the current project.
Are you the author of Handoff?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/suboss87-handoff)
---
name: handoff
description: Transfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.
---
# handoff
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
## Purpose
An operating handoff with ownership and a support path.
Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/close.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
## Principles
- Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
