Skip to content

Agent Operating Guide

/coach-item-create

Create a new item of any admin-configured type: schema-validated and submitted as one suggestion for a human to approve.

Create a single item of any admin-configured item type. The skill reads the type’s schema, gathers the required fields (interactively if you don’t supply them), validates your values against the field definitions, and submits one suggestion for a human to approve: nothing is written to your tenant directly.

When you want to open a new record of a known type: an audit, risk, control, issue, policy, or process. To create many items at once (for example, a starter pack), use the admin Bulk Import page instead; that path is not gated by suggest_change.

Flag Required Notes
--type <slug> If not clear from context The item type’s slug, e.g. audit, risk, control. If absent, the skill asks.
--values <json> No A JSON object of field keys to values. Partial is fine: the rest is gathered interactively.
--reason <text> No One sentence for the suggestion’s reason, to help the approver decide.

/coach-item-create --type risk reads the risk type’s schema, asks for each required field it doesn’t already have (title, severity, owner…), then submits a create suggestion. You review and approve it in Canvas: the item doesn’t exist until you do.

  • Field keys are case-sensitive: phase is not Phase. The skill uses the schema’s exact casing.
  • RELATION and USER fields take the related record’s id, not its title or name; the skill resolves a name or title to an id with a lookup before submitting.
  • Dates use ISO 8601 (YYYY-MM-DD); MULTISELECT values are the option value strings, not their labels.
  • Almost every type has a required title. If you describe an item without naming it, the skill drafts a short title and confirms it with you rather than inventing one.