Skip to content

Track progress

Every slice carries a status that says how far along it is. Together, the statuses tell the team what is settled, what is being built and what is stuck, without anyone having to ask.

  1. On the event model board, find the slice. Its status shows in its header.

  2. Select Change status in the slice header.

  3. Choose the new status.

The status menu of the AddToBasket slice listing Not started, Draft, Analysis, Ready for implementation, In progress, Ready for review, Done, Blocked and Waiting for user interface
A slice moves through the statuses from Not started to Done. Blocked and Waiting for user interface are for work that cannot go on yet.

The statuses are Not started, Draft, Analysis, Ready for implementation, In progress, Ready for review, Done, Blocked and Waiting for user interface. Statuses and colors explains what each one means.

Choosing Blocked opens Block slice with two questions: Why can it not be built? and Questions that need an answer, one per line. Write the reason and the questions the team has to answer before work can go on. The reason and the questions show on the Progress board.

  • While a slice is assigned to the System member or to an AI agent, Studio moves the status along and says Studio manages this status while the slice is assigned to the System member or an agent.
  • While Studio is generating a slice, its status cannot be changed until the generation has ended.

Assigning says who is responsible for a slice.

  1. Open the slice’s menu with Slice options.

  2. Choose Assign to, then pick who gets the slice.

The Assign to submenu of a slice listing the System member, the agents and the people of the organization
A slice can go to the System, to an AI agent or to a person. People's names are blurred here.

The list starts with the System member, then the AI agents that can generate code, then the people of your organization. Once a slice has an assignee, its menu offers Reassign and Remove assignee instead.

Assigning a ready slice to the System starts static code generation, and assigning it to a code-generation agent starts AI implementation. Assigning it to a person starts nothing. Generate and review code explains the rest.

The Progress board shows all slices of a project in one place, one column per status.

  1. Select Project options next to the project name in the top bar.

  2. Choose Progress board.

The Project options menu open next to the project name in the top bar
The Progress board is in the Project options menu.

Every slice is a card with its name and where it lives: its event model, module and feature. A column header shows how many slices are in it. A column with no slices says No slices. A blocked slice shows its reason and its questions under the heading Questions that need an answer.

The Progress board of Acme Commerce with a column for each status and the slices of all five applications as cards
The Progress board of Acme Commerce. Use the three filters at the top to narrow it down.

Use the filters at the top, All event models, All modules and All features, to look at one part of the project. The board is for reading: change a slice’s status on the event model board.

If your team tracks work in GitHub, Jira or Linear, you can link a slice to an issue and have the slice and the issue follow each other’s status.