Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-workflow-template-create

Author a reusable workflow template, ordered steps with optional per-step forms and decision branches, submitted as one suggestion for a human to approve.

Author a reusable workflow template: a blueprint of ordered steps that can later be instantiated under any item. The skill gathers the template’s name, description, and steps (each with a label, description, and instructions), optionally attaches a form or a decision branch to any step, and submits one suggestion for a human to approve. Once approved, the template joins your tenant’s catalog.

When to use

Section titled “When to use”

When a workflow will be reused across many items: an org-wide standard like a fieldwork or incident-response pattern. To attach the finished template to an item, use /coach-workflow-attach; for a one-off workflow that won’t be reused, use /coach-workflow-build.

Inputs

Section titled “Inputs”
Flag Required Notes
--name <text> No Template name. Asked if absent.
--description <text> No 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. Generated linearly from the step order if absent.
--is-public <bool> No Visibility. Defaults to private (creator and admins only); asked if absent.

Example

Section titled “Example”

/coach-workflow-template-create --name "Audit Fieldwork" walks you through each step, its label, description, instructions, and whether it needs a form, then asks whether the template should be public before submitting a create suggestion. The summary reads something like “Template drafted: 6 steps, private.” After approval, instantiate it under items with /coach-workflow-attach.

Good to know

Section titled “Good to know”
  • Steps can carry forms. Any step may include a fillable form the assignee completes after the workflow is instantiated; the platform copies the form onto the instantiated step so it renders at the step’s form URL.
  • Decision steps branch at run time. A decision step carries a SELECT field whose options are the branch values, with two or more outgoing branches. Build both branches: when the decision resolves during execution, /coach-workflow-execute fires a prune-branch op that deletes the not-taken one. The template keeps both; each instance keeps only the path taken.
  • Private by default. Public templates are visible to every user in the tenant (good for org-wide standards); private ones are visible only to the creator and admins (good for drafts). Most templates start private.
  • Creation only. To edit an existing template, submit an update suggestion against it: this skill authors new ones. Instantiated steps start unassigned; set approvers and due dates with /coach-workflow-assign.
Section titled “Related”