An agent specification cannot repair a fuzzy opportunity.
Before architecture, record the workflow, owner, consequence, evidence, exceptions, systems, human decisions, constraints, current measures, and what has already been attempted. This is the minimum context needed to decide whether an agent belongs in the solution at all.
Make uncertainty part of the record.
Known facts, assumptions, conflicts, and missing evidence should not collapse into one confident narrative. The useful output is a reference hypothesis plus the next questions needed for a person to approve, change, or reject the route.
Bind to the platform late.
Keep the opportunity, human boundary, outcome contract, and control intent portable. Bind to Microsoft, UiPath, Anthropic, Automation Anywhere, Pega, or a custom stack only after the route and client constraints are explicit.