Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-handoff-log

Compile everything a departing person owns across every shared-core item type into one shareable markdown handoff, item state, next action, stakeholders, and outstanding workflow Steps, after a light redaction pass.

Build the Canvas half of a departure package. When someone goes on leave or transfers, the skill assembles everything they own, across audit, issue, risk, control, process, policy, and authority_source items, plus the workflow Steps they’re assignee, watcher, or approver on, into one structured markdown document, capturing each item’s status, next action, key stakeholders, and blockers. It queries Canvas read-only and writes a single local file; it never mutates your tenant. The file runs through a light redaction pass and is not auto-shared: you review it, then choose how to hand it off.

When to use

Section titled “When to use”

Before a person goes on leave or transfers, to hand a covering person a complete picture without them rediscovering it from calendars and chat. It’s idempotent, so re-running it is also a useful status check. Needs the shared-core starter pack in place; run /coach-starter-pack first if pre-flight fails.

Inputs

Section titled “Inputs”
Flag Required Notes
--user <user-id|email> Yes The departing person.
--coverage <user-id|email> No Who’s taking over.
--start <YYYY-MM-DD> No When coverage begins. Default today.
--end <YYYY-MM-DD> No When coverage ends. Default open-ended.
--out <path> No Where to write. Default .coworkcanvas/handoffs/<user-slug>-<date>.md.

Example

Section titled “Example”

/coach-handoff-log --user michael@bluth.com --coverage gob@bluth.com pulls every item and Step Michael holds an active role on, groups them by item-type domain, and writes .coworkcanvas/handoffs/michael-<date>.md: a summary count, a hot-items list sorted by days-until-breach, per-domain sections, and a “What I’d do first” starter. You review it, then share it with the covering person.

Good to know

Section titled “Good to know”
  • It enumerates the Step surface, not just parent items: a person may own three audits but be assignee on forty Steps across their workflows, and every one is listed.
  • The file runs through a light redaction pass before you see it, because covering people don’t always share the departing person’s access.
  • It’s read-only and the file is never sent for you: hand it off however you like (a chat DM, an email draft, an in-person walkthrough).
  • “What I’d do first” is generated heuristically: treat it as a starting point, not gospel.
  • This is the Canvas half of a departure. The vault half: the person’s personal notes, open todos, and key contacts: is /brain-handoff in the Second Brain plugin; a complete handoff runs both.
Section titled “Related”