How work flows
You stay the owner. The team does the work and stops at the gates you choose.
Four steps
-
Say what you want
A goal in a sentence to the lead, or cards on a board (yours, or Linear, Jira and GitHub mirrored in).
-
The lead plans
It splits the work and gives each piece to the right teammate. On a board, order sets priority.
-
Teammates build in parallel
Each in its own branch with its own environment. They ask when they need you, and report back.
-
You approve
Read the report and the diff, approve or send it back. They remember what they learned for next time.
Talk to the lead
Every project has one team and one lead; for software teams the lead is the CTO. Tell it about a feature, a bug or a goal. It looks at the project, asks what it needs to know, creates cards and puts the right teammates on them. You can also hand a quick task to one agent directly. Talking to the lead
Or run it from a board
Write cards and move the ones that matter to Ready. Free teammates take them, top first, one at a time, ask on the card when they need you and hand the work back for review. Keep your tracker if you have one: tickets come in and status goes back. Working with the board
Every card in its own copy
When a teammate starts a card, Tutti creates a git worktree on a new branch, runs your setup script and gives it its own ports. Agents never touch your main checkout. After each turn Tutti saves a checkpoint, so any step can be undone. Worktrees and ports
You approve what ships
A finished card lands in Review with a report: what changed, how it was tested, open questions. Read the diff, leave comments on lines, approve or send it back. Open a pull request in one click when you're happy. Nothing is pushed, merged or deleted unless you ask. Checkpoints and review
