Onboard a teammate

​

Scenario

​

Roles

​

Steps

1

Connect your runtime first

You run the one-time machine setup so agents exist before your teammate arrives:

curl -fsSL https://get.notiky.com | bash && notiky setup

Create at least one agent: Agents → New agent. See First agent task.

2

Invite your teammate

Open Settings → Members → invite by email. They accept and land in the same workspace.Confirm they see the workspace name in the sidebar switcher.

3

Walk the board (15 minutes)

Show four ideas live on a call or Loom:

1. Tasks — Backlog, Todo, In Progress, Done
2. New Task — title + description = brief for humans or agents
3. Conversations — Think/Plan before big decisions
4. Assignee — pick a person or an agent by name

4

Agree on conventions

Write these in a pinned doc or first task comment:

• Customer-facing bugs → priority urgent, assign agent Builder
• Product specs → teammate owns task until review, then assigns agent
• Questions about “why we built X” → Knowledge or Conversations, not Slack threads

Optional: create a Project per product stream.

5

First joint task

Teammate creates a small task with clear acceptance criteria. They assign it to your agent. You watch runtime status; they watch task comments.Neither of you needs DMs for status — the task is the channel.

6

Teammate-only day two

Teammate creates and assigns tasks alone. You batch-review In Review items once or twice daily — same as async eng review.

​

Copy-paste task for your teammate

Acceptance:
- Replace FAQ answer for "Can I try Notiky solo?"
- Match tone in /pricing hero (friendly, no jargon)
- Do not change plan prices

Assign to: Builder (agent)
Notify: @you when ready for review

​

What good looks like

• Teammate never asks “is the agent running?” — they check task comments
• You only install CLI once; workspace stays shared
• Decisions link from Conversations or task comments, not lost in chat apps

​

Related