Skip to content

Agent Operating Guide

/coach-workflow-attach

Instantiate a workflow on an item from a reusable template: steps auto-generated and submitted as one suggestion for a human to approve.

Attach a workflow to an item, instantiated from a reusable template. The skill resolves the parent item (by id or title), picks a template from your tenant’s catalog, and submits one suggestion that creates the workflow instance with its steps auto-generated from the template: nothing is written to your tenant until a human approves it.

When you want to run a standard, reusable workflow on an existing item, for example, attach the standard audit fieldwork workflow to an audit. To design a one-off workflow that isn’t worth saving as a template, use /coach-workflow-build instead. To author the reusable template itself, use /coach-workflow-template-create.

Flag Required Notes
--item-id <id> or --item-title <text> One of the two The parent item the workflow attaches to. Narrow a title match with --item-type <slug>.
--template-id <id> or --template-name <text> No The template to instantiate. If neither is given, the skill presents the catalog to pick from.
--name <text> No Override the workflow name. Defaults to the template’s name.
--reason <text> No One sentence for the suggestion’s reason, to help the approver decide.

/coach-workflow-attach --item-title "Q2 Vendor Audit" --template-name "Audit Fieldwork" resolves the audit, finds the fieldwork template, and submits a create suggestion for a workflow whose steps are copied one per template node. You approve it in Canvas; the steps land in PENDING with no approvers yet.

  • Steps start unassigned. Instantiating a template creates one step per node, all in PENDING with no approvers or due dates. Set them next with /coach-workflow-assign.
  • Naming convention. Templates carry generic names like “Audit Fieldwork”; prepend the parent item’s identifier so the instance is recognizable in lists, “Audit Fieldwork, Q2 Vendor Audit”. Convention, not enforced.
  • Template or from-scratch, not both. A template attach and a hand-authored node/edge graph are mutually exclusive: the platform rejects a suggestion that sets both. For the hand-authored path, use /coach-workflow-build.
  • Then execute. Once attached and assigned, run individual steps with /coach-workflow-execute, which enforces upstream completion before a step can run.