I think the actual loop engineering lives in skills and workflows. The trigger is the creation of a ticket, manual or programmatic; e.g., through an incident.

Your perspective here is of a software engineer only, and I gets it, for software engineering you got a great point and I somewhat agree with it. When we talk about how to work with agent the holy grail is agent’s pro-activity, one of the columns of pro activity is webhooks as you said “the creation of a ticket”, I don’t want to attack this vector, I what to be laser focus on the scheduling vector as I said in another comment here.

Regarding skill and workflows, I don’t want to make you couple your way of work to the routine, if you want to load the the workflows and skills feel free, in the end of the day the routine is only a scheduled prompt.

Would love to hear more about your way of working with event driven actions