sunshineDefine the goal through the deliverable
Sun-Shine’s Agent Factory approach breaks an Agent down into goals, capabilities, data, tools, workflows, permissions, and verification mechanisms. For a task such as organizing inquiries that need follow-up, first agree on which customer records, missing information, and suggested actions the deliverable should contain, and who will accept it. This makes completion assessable.
Set boundaries for data and actions
List the customer information the task needs to read, the tools it may use, and the destinations it may write to. Define authorization and approval conditions for actions such as sending external messages or changing customer status. When information is insufficient, return a list of missing items instead of inventing customer requirements or treating generated suggestions as permission to act.
Plan for interruptions and failures
The workflow should distinguish states such as pending, running, awaiting approval, complete, and failed. When information conflicts, a tool is unavailable, or a write fails, record completed steps and unfinished work so the owner can decide whether to supply information or resume execution. Before resuming, check for existing successful results to avoid duplicate messages or writes.
Complete delivery through acceptance and write-back
During acceptance, check that customer records have sources, missing information is clearly identified, suggestions stay within permissions, and written results match expectations. Write confirmed results and processing status back to the designated system, then collect exceptions as material for future improvements. This is a task design method supporting the long-term Agent OS direction, not a claim that every capability is already available.