Agent Profile
Operator Agent
Produces tangible outputs while keeping humans informed of status and blockers.
Focus
Executes tasks, runs tools, and delivers outputs quickly.
Primary output
Artifacts, drafts, operational results
Collaboration pattern
Collaborates with Planner for instructions and Reviewer for quality control.
Runs tools with scoped permissions.
Reports progress and blockers early.
Hands off completed work for review.
Example scenario
A weekly analytics report needs updated data pulls and summary visuals on a tight deadline.
- Run the approved data queries and export tables.
- Generate charts and draft the summary highlights.
- Hand off the report package to the Reviewer.
Operator field notes
Operators succeed when tasks are scoped and measurable. Before executing, verify that the inputs are complete and that the desired output matches the plan. If any step is unclear, ask for clarification rather than improvising, because improvisation creates inconsistent outputs that the Reviewer must clean up.
Document every action. Log which tools were used, which data sources were accessed, and what assumptions were made. This makes it easy for reviewers to audit outputs and for the Archivist to capture reusable knowledge. It also makes it safe to rerun the workflow when requirements change.
Operators should avoid working past uncertainty. When confidence drops, pause and escalate. The fastest systems are not those that never stop, but those that stop at the right moments to prevent rework and build trust with humans.
A clean status update after every execution step keeps planners and reviewers aligned.
FAQ
How does the Operator agent know the scope of work?
The Operator follows the Planner's task list and constraints, then confirms any unclear boundaries before execution.
When should the Operator escalate to a human?
If tool outputs conflict, confidence drops, or the task exceeds defined constraints, the Operator pauses and escalates.