Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-field-builder

Add fields to an existing item type interactively, written to your schema JSON in the platform's bulk-import format.

Add one or more fields to an existing item type. The skill walks you through each field’s key, label, type, whether it’s required, any options, and the flags that control where it shows up (on list cards, in filters, in full-text search), then updates your workspace schema JSON in bulk-import format. Like item types, fields are an admin-page concern: you apply them by pasting the schema at the admin Bulk Import page, not through suggest_change.

When to use

Section titled “When to use”

When an item type needs a field it doesn’t have yet: a new SELECT, a relation to another type, a date. For SELECT options you want to share across several types (severity, priority), use /coach-custom-list instead so the list is reusable.

Inputs

Section titled “Inputs”
Flag Required Notes
--type <slug> Yes Which item type to extend.
--field <fieldKey> No Single-field, non-interactive mode. Otherwise the skill adds fields one at a time until you’re done.

Example

Section titled “Example”

/coach-field-builder --type control adds fields one at a time, say a testFrequency SELECT with daily/weekly/monthly options and a relatedRisk RELATION pointing at the risk type, mapping your plain-language answers to the platform’s field types, then validating the schema before you paste it at /en/admin/bulk-import.

Good to know

Section titled “Good to know”
  • Only the platform’s field-type enum is valid, spelled exactly: TEXT, TEXTAREA, RICHTEXT, NUMBER, DATE, DATETIME, SELECT, MULTISELECT, BOOLEAN, USER, USERS, RELATION, RELATIONS, JSON. There’s no URL, FILE, EMAIL, or CHECKBOX: store URLs and emails as TEXT, use BOOLEAN for a checkbox, and attach files via upload_document at fill time. A value outside the enum fails at import.
  • Fields go under FieldDefinition (capital F, capital D); the legacy lowercase fields array is silently dropped. RELATION/RELATIONS fields use relatedItemTypeSlug, not the legacy relationTarget.
  • Don’t mark every TEXT field searchable: it inflates the search index and slows queries. The skill confirms before flagging any non-title TEXT field searchable.
Section titled “Related”