The board

In the portal, under Environments, click Development, and there Open. Flow opens in a new tab and you are signed in straight away.

In the bar on the far left is Board. A new board is empty and says in one sentence what it is for, with one button to start.

Click Add the first item (later: New, top right). Choose the kind Epic: the big goal, for example a new customer journey. Give it a title and click Create. The epic gets a lane of its own on the board, with its progress, and is in the side bar under Epics.

Click New and choose Feature: a recognisable part of the epic. Under Belongs to you choose the epic. You do not move a feature yourself: it sits as a label in its epic's lane and counts how many of its items are done.

Click New and choose Item. Under Belongs to you choose the feature, and under Description you write what needs to happen and why (at least 20 characters). After Create the item opens on the right in the inspector. On the tab Story, add an acceptance criterion: when is it right? On the tab Ready? you see whether the item is ready to commit.

The inspector keeps an item clear in four tabs. Story: the description and the acceptance criteria (for an epic or feature also its parts). Properties: the status, the owner, the estimate, what it belongs to, what it waits for, the links and the mirrors. Ready?: the checks with what to do about them, and an AI Colleague that can build the item. Conversation: the comments and the history. A number on a tab says what is waiting, such as open checks or comments. Flow remembers which tab you chose last, and a button like Add acceptance criteria takes you to the right tab by itself. With the keyboard you choose a tab with the arrow keys.

To read or write calmly, click Open as page at the top right of the inspector (the icon with the four corners). The whole item opens large: on the left the title, the description and the acceptance criteria, with the conversation and the history below; on the right the properties, Ready? with the checks, the links and the mirrors. You change everything there just as in the inspector, and it is saved the same way. Esc closes the page; on a narrow screen everything is stacked.

When two people work on the same item at the same time, Flow never silently overwrites the other's work. What someone else saves appears straight away, without losing what you are typing. When you each change a different field, everything is kept. When the other person just changed the same field, Flow keeps the rest and shows at that field who changed it and to what: you keep that value, or choose Save my value. The same goes for an AI app, and for yourself in another window, as here.

Take hold of the card and drag it to Grooming. The column under the card lights up when the step is allowed. No question beforehand; at the bottom Undo shows for a while, in case it was a mistake.

Tab to a card. Space picks it up, the right arrow chooses the next column (Drop here), Enter drops it and Escape cancels. A screen reader reads every step aloud.

Drag the return label to Committed. Flow only commits an item when it is ready; this item has no acceptance criteria yet. The card stays where it is and says what is missing, with a button per check that takes you straight there.

Click Add acceptance criteria: the item opens in the inspector on the tab Story, with the cursor where the criterion goes. Type it and press Enter. Now it is ready: drag the card to Committed again.

Open Version control. Below the message is Which items does this version deliver?, suggesting what is in progress or in review; you can find another item too. Tick the confirmation mail, write what you changed and click Commit. An item's code in the message links it as well (see the next step).

Click the delivered item: the board opens with the item in the inspector. On the tab Properties, under Linked is the version, with its number and message. That way you see for every piece of work which version it is in, and for every version which work is in it. Top right in the inspector is the item's code (#…): click it to copy it, and put it in the message of a version to link the item without ticking it.

In the portal you promote the version to Acceptance: under Environments with the arrow between Development and Acceptance (or under Releases). The release takes along which items the version delivers: title and status, never the comments.

Click Acceptance and there Open, and in Flow open Version control. At the top of the history is the release from Development; click it. Under Delivered items is what this release delivers. The board itself stays in Development: that is where the work happens.

With MCP access (Read and Build) an AI app such as Claude Code works on the board with your rights. The recipe Working from the board in the app's guide: read the board with list_work_items and get_work_item, create or update an item with save_work_item, move it with move_work_item and link the work with link_work_item. When Flow refuses a step, the app gets the checks that fail and what to do about them: here the app then added the acceptance criteria and committed the item.

Click New, choose Item and under Template User story. The template fills the description and the acceptance criteria with placeholders like ‹role›, ‹goal› and ‹value›: ‘As a ‹role› I want ‹goal›, so that ‹value›’, with criteria in Given / When / Then. There are templates for a bug, a research item (spike) and an epic or feature too; owners and administrators keep templates of their own under More → Manage templates. As long as a placeholder is in it, the item is not ready: the check on the tab Ready? names what still has to go in.

On the tab Story, next to the description, click Expand. On the left you write, on the right you see straight away how it looks; the buttons above make headings, lists, tasks, a table, code and links, and mention a colleague (@) or another work item (#). Next placeholder (⌘J) jumps to the next ‹…›. Flow keeps what you write as a draft in this browser on the way; Save (⌘↵) records it, Esc cancels.

Customers call customer service because they lost the mail.

• An app of its own for the phone`

Above the editor is the AI help: Write as a user story, Suggest acceptance criteria, Make it more concrete, Make it shorter, Split into smaller items and Check for completeness. Choose Suggest acceptance criteria. This environment's AI Colleague makes a proposal and Flow shows the difference with what is there now. Nothing changes without you: Accept puts it in the window, Reject leaves everything as it was. Then click Save.