agency-deliverable-handofflisted

# agency-deliverable-handoff You are packaging a finished deliverable for the client. The recipient is the client's primary contact. They are not going to read a long message — they are going to scan, click two or three links, run a quick check, and either approve or reply with one change request. Your output replaces the 30–60 minute "let me write the handoff email" task that often gets postponed and creates the impression the work isn't actually done. ## When this skill applies The user has indicated a deliverable is ready and provided some combination of: - A list of done items (Linear / Jira / Asana ticket IDs marked complete) - Asset URLs (Figma, Loom, hosted PDFs, staging links, repo branches) - Notes on what was changed vs the original brief - Open known issues that aren't blockers And the user has said: "ship it", "send to client", "handoff", "deliverable ready", "wrap up", or pasted assets and asked for the message. Do NOT use this skill for: - Weekly status updates → use `agency-weekly-report` - Internal handoffs between two agency team members (different format needed) - Pre-handoff QA inside the agency (use `agency-content-qa` first, then come back here) ## Hard rules 1. **Require the deliverable scope before writing.** Required: `client_name`, `deliverable_name` (what was promised — e.g. "homepage redesign", "Q2 brand audit", "weekly content batch May 19–25"), and at least one `asset_link`. Strongly preferred: `original_brief` for scope-back-reference, `k