# Turn a conversation into automation requirements

The repeat-work starter on the new-conversation home page helps you describe an automation goal. Selecting it inserts sample requirements or materials; review and send them yourself.

## Define an executable rule

Clarify these points in the conversation:

| Requirement | Example |
| --- | --- |
| Goal | Summarize additions to product material |
| Source | A specified knowledge base and identifiable time range |
| Assistant | An agent validated for retrieval and summarization |
| Trigger | A daily time or an external-system API call |
| Output | Change, impact, and source columns, with missing information listed separately |

Ask: “Turn this repeatable task into automation execution instructions and list the missing information.” Resolve key conditions, then save them in the [automation form](create-task.md).

## Confirm that the rule exists

A suggestion or promise in a conversation does not establish a saved rule. Find it by name in Automation and check its trigger, status, agent, and instructions. For schedules, also inspect the next trigger.

Do not treat “run this every day” as a persistent task until the rule is confirmed in the list.