Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-workflow-assign

Assign approvers and due dates across a workflow's steps, resolving people by name or email and submitting one suggestion per step for a human to approve.

Set approvers and due dates on the steps of a workflow instance. The skill walks the workflow’s steps, resolves the people you name (by name or email) to user ids, and submits one suggestion per step that sets its approvers and due date: a batch you approve together on the suggestions dashboard. Nothing changes until you approve.

When to use

Section titled “When to use”

When a workflow’s steps exist but nobody’s assigned yet: the typical “assign them all at once” pass right after /coach-workflow-attach or /coach-workflow-build. Use it whenever you need to set deadlines or pick approvers for a workflow’s steps.

Inputs

Section titled “Inputs”
Flag Required Notes
--workflow-id <id> or --workflow-name <text> No The workflow instance. If absent, inferred from your current view.
--assignee <name|email> No The approver for all steps, when one person covers the whole workflow.
--due-by <ISO 8601> No The final due date. Set without per-step dates, the steps are spread evenly between today and it.
--per-step <json> No An array of { stepName, assignee, dueDate } for explicit per-step control.

Example

Section titled “Example”

/coach-workflow-assign --workflow-name "Q2 Fieldwork" --assignee alice@firm.com --due-by 2026-07-15T17:00:00Z fetches the workflow’s steps, resolves Alice to her user id, spreads the due dates evenly up to July 15, and emits one update suggestion per step. The summary reads something like “Assigned 5 steps to Alice, all due by 2026-07-15.”

Good to know

Section titled “Good to know”
  • Due dates need a full ISO 8601 datetime with a timezone: 2026-07-15T17:00:00Z, not 2026-07-15. A date-only string is rejected. When you say “next Friday at 5pm”, the skill resolves it to a concrete datetime and confirms before submitting.
  • One suggestion per step. The platform has no bulk-assign endpoint, so each step is its own suggestion. You can approve all of them or just some: partial application is fine.
  • Multiple sign-offs. To require sequential approvals, assign several approvers with ascending review levels; a higher level approves only after the lower ones. The number of approvers sets the step’s required-approval count.
  • Completed steps are skipped. The platform rejects approver changes on a COMPLETED step (its approval history is immutable), so the skill doesn’t try.
Section titled “Related”