Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-workflow-build

Author a one-off workflow on a single item by writing its steps from scratch, submitted as one suggestion for a human to approve.

Author a workflow directly on an item by writing its step nodes and their connections yourself: no template involved. The skill resolves the parent item, walks you through the steps (label, description, instructions), wires them into a flow, and submits one suggestion for a human to approve. Nothing is written until it’s approved.

When to use

Section titled “When to use”

When a workflow is specific to one item and doesn’t warrant a reusable template: a one-off engagement, a particular project, a unique incident response. To instantiate an existing template instead, use /coach-workflow-attach. If the workflow will be reused across many items, author it once with /coach-workflow-template-create and attach it.

Inputs

Section titled “Inputs”
Flag Required Notes
--item-id <id> or --item-title <text> One of the two The parent item. Narrow a title match with --item-type <slug>.
--name <text> No Workflow name. Asked interactively if absent.
--description <text> No Optional one-paragraph description.
--nodes <json> No Pre-built step array. Gathered interactively, one step at a time, if absent.
--edges <json> No Pre-built connections. Defaults to linear (each step → the next).

Example

Section titled “Example”

/coach-workflow-build --item-title "Q2 Vendor Audit" resolves the audit, then walks you through each step one at a time, its label, an optional description, and the instructions the eventual assignee will follow, before wiring them linearly and submitting a create suggestion. The summary reads something like “Workflow drafted: 5 steps under audit Q2 Vendor.”

Good to know

Section titled “Good to know”
  • Steps start unassigned, in PENDING. Set approvers and due dates with /coach-workflow-assign, then run steps with /coach-workflow-execute (which enforces upstream completion).
  • Linear by default; branching is supported. If steps run in parallel: “step 2 and step 3 both must finish before step 4”: the connections reflect that and the platform’s auto-layout handles rendering. You don’t set node positions; they’re auto-calculated.
  • Naming convention. Prefix the workflow with the parent item’s identifier so it’s recognizable in lists, “Q2 Audit, Walkthrough” beats “Walkthrough”.
  • Changed your mind about a template? Hand off to /coach-workflow-attach: this skill never sets a template id, and the two paths are mutually exclusive.
Section titled “Related”