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.
Start a fresh conversation. Replace the highlighted placeholders.
Use handoff to draft an operational handoff summary for [project/deployment context], including ownership, a '2am' operating guide with observed failures and recovery steps, and a list of unresolved readiness gaps based on [supplied evidence or operating notes].
Required inputs
[project/deployment context]
[supplied evidence or operating notes]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: handoffdescription: 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
Purpose
An operating handoff with ownership and a support path.
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.