Agent Operating Guide
/coach-form-fill
Pre-fill an existing step form with AI-suggested values the assignee can edit and submit in one click.
Propose values for an existing workflow-step form, drawn
from the conversation, a transcript, or another source, so the assignee sees the
suggested fill on the form page, edits any field, and submits in one click. The fill is
written through review via the submit_form action of
suggest_change, which routes the preview to the form
page rather than the generic suggestion viewer. This skill fills a form; to author or
change its fields, use /coach-form-create.
When to use
Section titled “When to use”When you want to populate, pre-fill, fill out, draft, or submit values for an existing step form. To create the form or change which fields it has, use /coach-form-create instead.
Inputs
Section titled “Inputs”| Flag | Required | Notes |
|---|---|---|
--step <stepId> |
Yes | The step whose form you’re filling. |
--values <json> |
No | A JSON object of field keys to values. Gathered from the conversation if absent. |
--rationale <text> |
No | One sentence explaining the fill, to help the assignee decide whether to accept. |
Example
Section titled “Example”/coach-form-fill --step <id> --values '{"control_effective":"yes","test_notes":"…"}'
reads the step’s form schema, validates the values against it, and submits a
submit_form suggestion. The assignee gets a Review and submit form link to the form
page, where they can edit any field and submit in one click.
Good to know
Section titled “Good to know”- Values are validated up front against the schema: missing required fields, bad select values, or file ids that don’t belong to the step are rejected before the suggestion is created. Read the error rather than retrying blindly.
- Use the schema’s exact field keys: they’re case-sensitive, with no aliases.
- The preview always routes to the form page, not the generic suggestion viewer:
that’s what the
submit_formaction guarantees. Approving there and clicking Submit are the same write. - File fields take document ids. Upload the file with
upload_document first, then pass
[documentId]; file bytes are never inlined into values. - Re-filling a submitted form is allowed: the skill asks before overwriting, and the prior values stay in the audit log. External assignees fill the same way once they sign in.
Related
Section titled “Related”- /coach-form-create: author the form’s schema first.
- /coach-document-upload: upload a file to reference in a file field.
- suggest_change: the
submit_formaction routes the fill to the form page. - Forms: how step forms and their fields work.