Design patterns help when trying to quickly implementic agentic use cases. I call this design pattern "Collect and Create". The fundamental use case is that some amount of information needs to be collected first, and then something (e.g., report, Jira ticket, Slack post) gets created afterwards.
The user starts by posting an initial set of information or request. The agent checks to see if the necessary information is present. If not, then the agent asks the user to provide the necessary information. If yes, then the agent creates the desired end product with all of the information provided.
As an example, let's say that the IT department had a very specific process for alerting employees about IT issues. The agent would ensure that all of the necessary information was available for what the IT issue was, who it affected, what services were affected, and what actions needed to be taken. The agent wouldn't move on to the creation step until all of the information was available to the agent. After all of the information was available, then the agent would create the IT alert. For example, the agent could search for prior similar IT alerts for examples, and then follow a set of rules for writing the IT alert in a consistent format and style.
