Instructions apply to every chat and Pulse for a Coworker. Put stable rules in Instructions and task-specific details in the chat or Pulse prompt.
Workspace owners and admins can edit them from the Coworker’s Settings. Use Improve with AI to revise an existing draft.
A useful instruction structure
- Role and objective: what the Coworker is responsible for.
- Sources: which Knowledge, Data, Connectors, or MCP servers to use.
- Procedure: the order in which to complete the work.
- Boundaries: actions to avoid or confirm first.
- Output: required format, detail, and destination.
- Missing information: when to ask, stop, or flag uncertainty.
Prepare the weekly vendor-risk brief. Use the approved vendor Knowledge sources before connected spreadsheets. List newly added vendors, overdue reviews, and records missing an owner. Never mark a review complete. If source values conflict, cite both values and flag the vendor for an admin. Return a summary followed by a table with vendor, risk, owner, due date, and issue.
Test instructions before scheduling
-
Run a normal case
Use representative data and confirm the Coworker follows source priority and output format.
-
Run an incomplete case
Remove or omit a required value. Confirm the coworker asks, flags, or stops as instructed.
-
Run a boundary case
Request an action outside the Coworker’s authority. Confirm it refuses or seeks approval.
-
Refine the smallest rule
Change the instruction responsible for the failure, then rerun the same case before adding a Pulse.
Common instruction problems
Avoid conflicting rules and vague terms. Replace “prioritize urgent items” with a definition of urgent. Name preferred sources and explain what to do when they disagree.