Writing good role descriptions
A coworker runs on exactly what you write in its instructions. Practical advice for the instructions, rules, examples and starter tasks, with a complete example in English and in Japanese.
3 min read
Where you write itCopy link to this section
In the builder, Role & instructions is what the coworker runs on. Guided gives you separate boxes for the instructions, tone, reply language, rules and examples; Plain text is one box. Either way the whole thing is limited to 1,000 characters, and passwords and keys are refused: give those through the private sign-in instead. Up to three Starter tasks of 120 characters each appear as suggestions when someone starts a conversation with it.
What makes instructions workCopy link to this section
- Name the job and who it is for in the first line: “You prepare expense claims for the Tokyo sales team.” One coworker, one job; make a second coworker for a second job.
- Say what “done” looks like: the format, the length and where the result goes. “A table with date, vendor, amount and category, saved to the Expenses folder.”
- Write rules as things to do or never do, one per line, and give the reason when it is not obvious: “Never submit a claim; leave it as a draft, because a manager signs it.”
- Tell it what to do when it is unsure: ask, or say what it could not find. A coworker that guesses quietly is worse than one that asks.
- Show one example of a good answer rather than describing it at length.
- Leave out what approvals already handle. You do not need “ask before sending”; set that in Approvals and boundary rules, where it is enforced rather than requested.
Example in EnglishCopy link to this section
You prepare expense claims for the Tokyo sales team.
When someone sends receipts, read each one and add a row to a
table: date, vendor, amount in yen, category (travel, meals,
supplies, other) and the receipt's file name.
Rules:
- Check each claim against the expense policy in Knowledge.
- Mark anything over the policy limit as "needs approval".
- Never submit a claim. Save it as a draft; a manager signs it.
- If a receipt is unreadable, say which one and ask for a new photo.
Reply in the language the person wrote in. Keep replies short:
the table, then one line per problem.Starter tasks for it: “Turn these receipts into a claim”, “Which of last month's claims are still drafts?”
Example in JapaneseCopy link to this section
あなたは東京営業チームの経費精算を準備する担当です。
レシートが送られてきたら 1 枚ずつ読み取り、表に 1 行ずつ追加します。
列は日付、取引先、金額(円)、区分(交通費・会議費・消耗品・その他)、
レシートのファイル名です。
ルール:
- ナレッジにある経費規程と照らし合わせて確認する。
- 規程の上限を超えるものは「要承認」と記載する。
- 申請は送信しない。下書きとして保存する(上長が承認するため)。
- 読み取れないレシートがあれば、どれかを伝えて撮り直しを依頼する。
相手が書いた言語で返信する。返信は簡潔に、表のあとに問題点を 1 行ずつ。Starter tasks, written in Japanese too: “Turn this receipt into an expense claim” and “Which of last month’s claims are still drafts?”
Try it before you create itCopy link to this section
Try it beside the builder is a test chat that runs on what you have written so far. Give it one of the starter tasks and a case that should be refused or questioned. If it guesses where it should ask, add a rule; if it ignores a rule, move the rule up and make it shorter. The draft is kept in your browser until you create the coworker.
Last updated