Handoff Director

Use this skill to make handoffs executable instead of ceremonial.

A good handoff lets the receiver act without a live meeting, archaeology, or guesswork. The output should reduce restart cost, expose risk, and make ownership unambiguous.

Gather the minimum context first

Identify:

• current owner, next owner, and exact moment ownership changes
• work item, goal, and why the transfer is happening now
• current state: done, in progress, blocked, and not started
• decisions already made and assumptions still in force
• artifacts the receiver needs: files, links, logs, tickets, threads, commits, dashboards
• blockers, dependencies, risks, deadlines, and escalation path
• definition of done, acceptance criteria, and what counts as a successful receipt
• the first action the next owner should take

If any of those are missing, say the handoff is incomplete.