Small teams

Keep a shared release, clear responsibility, and one record of decisions.

View as Markdown View this page as plain text

Who it's for

Two to ten people building one product together, each with their own coding agent. You need one plan everyone trusts, and to know who's doing what without a meeting.

RollCall has three people: Thomas, Maya and Sam.

Piece Example
Project RollCall, with Maya and Sam invited as members
Areas Groups & Social, Challenges & Feed, Punishments & Streaks, Notifications, Premium & Limits
Releases 1.1.0 active, 1.2.0 next. Each version is a set of changes you ship together.
Assignees The person moving each task forward

Use areas for the parts of the product that last ("Notifications") and releases for what ships next ("1.1.0"). A feature name like "Team invites" is a task, not a release.

Punishment reveal experienceDramatic reveal UI with animations, haptics, and confirmation. MC+1

Dramatic reveal UI with animations, haptics, and confirmation.

Improvement Punishments & Streaks 1.1.0 #8
  • A task can have more than one assignee. Here Maya and Thomas share #8.
  • Agree who moves it forward, so a shared task never waits on someone else.
  • The coloured chips show the area and release at a glance.

Get your team in

  1. Open the project's ⋯ menu and choose Share.
  2. Choose Create link, then Copy, and send it to your teammates.
  3. Each person opens the link, signs in or creates an account, and chooses Join project.
Everyone on the project is listed under the invite link.

The link works for a week. Members can do almost everything the owner can; see Team & invites for the few things only the owner can change.

A week in the loop

  1. Start the week on the active release. Check every open task has an assignee and nothing is blocked.
  2. Each person works their tasks, or hands one to their agent. Status changes show up for everyone straight away.
  3. Ask questions in the task's comments, not in chat, so the decision stays with the work.
  4. Review new signals together. Make tasks for the ones you'll do and leave them in the Backlog until they're planned.
  5. Complete the release when it ships and set the next one active.

Talk on the task

When Maya had a question about #7, she asked it on the task. Thomas answered there and added a subtask, so whoever picks it up next, person or agent, finds the decision with the work.

Comments sit in the task's Activity, next to every change made to it.

Status changes, edits and agent updates appear in the same list, newest first, so the whole history of a task is in one place. The dashboard's Recent Activity shows the same across the whole project.

Features that matter most

  • Team & invites: share an invite link from the project's ⋯ → Share. Indie allows 5 members per project, including you; Studio allows 10.
  • Tasks: assignees, subtasks and comments keep the detail on the task.
  • Views & filters: filter the board to one release or area, or change many tasks at once.
  • Connect your agent: each person connects their own agent, on any plan.
  • GitHub: write FB-8 in a commit or pull request to link it. Indie and above.

Next steps

Was this page helpful?

Last updated