Employees

Give an employee a job once, then reuse its instructions for the next task. Open Bots in the dashboard to create one.

Choose a role

Start with one of four editable templates:

Role	Try this first
Engineering	Fix a bug and add a test for it.
Marketing	Draft a launch brief and announcement copy.
Research	Answer a question using evidence you provide.
Operations	Write a release or recovery checklist.

Choosing a template fills in a draft. You can change its instructions before saving.

Create your employee

1. Open Bots and choose a role, or start with your own instructions.
2. Enter a name and unique slug (a short identifier). Describe what the employee should do and how it should check its work.
3. Review the default run settings and choose an available Model connection. Add a default GitHub repository if you usually work in the same one.
4. Review Required deliverables. These are files you expect the task to return.
5. Select Create bot.

Use Edit bot later to change the saved profile. Ask your Shiba operator for help if the connection you need is unavailable.

Start work

Select Launch bot. In the new thread, confirm the repository and describe the result you want. For example:

Draft a launch brief and three announcement options using the product docs in this repository. Cite the claims you use and list any missing evidence. Keep the copy as drafts for review.

Before work starts, review and approve the exact request on the approval card. Creating an employee does not approve its tasks.

When the task finishes, open the returned files and review the changes and checks. A draft campaign is not a published campaign.

Return to a conversation

Open the employee’s card and choose a conversation under Threads started with this bot. Keep related follow-ups there, or select Launch bot for a separate task.

Add another role

Create custom instructions for Design, QA, Sales, Finance, or other work your company needs. These are custom roles, rather than built-in templates in this version.

For Design, ask for a document covering user flows, interface copy, accessibility, and the states people may encounter.

For QA, name the feature and checks you want. Ask for observed results, reproduction steps, and anything that could not be tested. Available test tools depend on your setup.

For Sales, ask for an account brief or outreach draft using the information you provide. For Finance or revenue work, supply the figures and ask for a draft budget or performance summary you can check.

Next: Start and review a task or save reusable skills.