Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-template-library-manage

A central library for reusable workflow and dashboard templates: list, create, clone, update, archive, and restore them, with archived versions kept for historical reproduction.

Manage a central library of reusable templates: workflow templates that instantiate as the steps on an item, and dashboard templates that seed a saved view. The skill owns the whole lifecycle: list, create, clone, update, archive, and restore. Cloning a workflow template attaches a fresh workflow to an item and goes through a suggestion for a human to approve; the lifecycle actions on dashboard templates and on the library itself run as admin-page actions, not suggestions. It archives rather than deletes, so retired templates stay reachable for historical reproduction while new work uses the active version.

When to use

Section titled “When to use”

When you need the standard template for a job, a vendor-risk review, a fieldwork pattern, and a place to keep, version, and retire those templates over time. To author a brand-new workflow template’s structure, use /coach-workflow-template-create; to attach one to a specific item, use /coach-workflow-attach: this skill drives both and owns the lifecycle around them.

Subcommands

Section titled “Subcommands”
Subcommand What it does
list List templates, filtered by kind (workflow / dashboard), active or archived, and owner.
create New template: a workflow template from an item, a workflow run, or from scratch, or a dashboard template.
clone <template-id> Instantiate a fresh workflow on a target item (or a dashboard into your workspace) from the template.
update <template-id> Propose changes to a template, optionally learned from a recent workflow run.
archive <template-id> Mark a template archived: version control, not deletion.
restore <template-id> Flip an archived template back to active.

Example

Section titled “Example”

/coach-template-library-manage clone tmpl_fieldwork --target-item AUD-7 instantiates a fresh workflow on audit AUD-7 from the fieldwork template, its steps copied from the template, no historical run state, and submits it as a suggestion to approve. /coach-template-library-manage list --kind workflow prints the workflow templates with their owner, active/archived state, and which template each was derived from.

Good to know

Section titled “Good to know”
  • Clone is always a fresh workflow. A cloned workflow inherits the template’s step structure but none of any prior run’s state: it starts in-progress from scratch.
  • Archived isn’t deleted, and archiving doesn’t block cloning. Retiring a template just steers new work to the active version; you can still clone an archived one to reproduce historical work (the skill warns rather than refuses).
  • Version control is a chain of archives: archive v1, create v2 from a recent v1 run, and the derived-from link preserves the lineage.
  • Two write paths. Cloning a workflow template produces a suggestion to approve; list, archive, restore, update, and dashboard-template actions are admin-page actions and don’t.
Section titled “Related”