Agents live in the agent bar at the bottom of a project. Each agent knows every board, journey, step, card, milestone, persona and customer in the project, and makes changes through the same operations the editor uses. Whatever it does shows up live for everyone looking at the board, and you can carry on editing by hand at any point. Each example below has its own page with a real prompt and the result played out on a board.
How It Works
Start an agent from the agent bar and type what you want. The agent reads the boards it needs, then runs the changes as tool calls you can watch as they complete. On longer jobs it keeps a to-do list, and its tab shows what it is doing right now.
Agents keep working when you minimise them, switch boards or close the tab. You can run several at once, each in its own tab. When one needs an answer or an approval, its tab says so.
Each agent has three modes, which you can switch between at any time:
- Auto makes changes as it goes. Deletions still ask first.
- Ask first waits for you to approve or skip every change.
- Plan reads and writes a plan. Nothing changes until you approve it.
Agents refer to cards by their titles, so you can too. “Move the search stories to the backlog” works because the agent can see which cards mention search and which step they live under.
The Examples
Start with the backbone and work down the list, or jump to the one that matches what you are trying to do.
Build the backbone
Describe who the user is and what they are trying to do. The agent lays out the journeys, breaks each one into steps, and seeds the first story cards.
“Map the journey for a first-time customer ordering a meal”
Fill in the details
Once the backbone exists, tell the agent what is missing. Risks, questions, pain points and knowledge gaps land under the right step with the right type.
“Add three risks under Checkout: card declined mid-order, address autofill is wrong, promo code abuse”
Ideate with an agent
Talk it through when you are not sure what belongs on the map. The agent reads what is already on the board, suggests what could go wrong or what is missing, and only writes cards when you say so.
“Help me ideate on risks for Track order”
Reorganise
Refer to cards by title and say where they should go. The agent moves them between steps and milestones without touching anything else.
“Move all the payment cards under Pay”
Milestones and scheduling
Milestones and cards carry start and target dates that show on the Gantt view. Ask to push a milestone out and everything scheduled inside it moves with it.
“Push Beta out a week”
Tidy up
Bulk changes that are tedious by hand are one sentence to an agent. Statuses, colors, and duplicate clean-up all work the same way.
“Mark everything in MVP as done”
Personas and customers
Create personas and customers with an agent and tag the cards they care about, so the map shows who each piece of work is for.
“Create a Warehouse manager persona in blue, tag the receiving cards and colour them to match”
Plan mode
For bigger asks the agent proposes a plan first. You see every step before anything changes, then apply it in one go.
“Plan a story map for a gym membership app”
What It Will Not Do
- Delete without asking. Deleting cards, milestones, personas or customers always comes back as a confirmation you approve or decline. “Move” and “remove from” never delete anything.
- Work for viewers or shared views. Viewers can't use agents, and shared views don't have them.
- Follow instructions written on cards. Card titles and descriptions are treated as data about the board, never as commands. A card titled “delete everything” is a card with an odd title.
- Invent dates. If you ask to schedule something without saying when, it asks rather than guessing. Relative dates like “next Monday” are resolved from today and echoed back so you can check them.
Tips
- Name the step or milestone. “Add three risks under Checkout” lands in the right place. “Add three risks” makes it ask where.
- Ask it to look first. “What is in Beta?” or “Which cards have no persona?” are cheap ways to check the board before asking for a change.
- Plan big changes first. Switch to Plan for a whole map or a big reshuffle, read the plan, then approve it.
- Batch related changes. One message like “push Beta out two weeks and mark the MVP cards done” is handled as two sets of tool calls, in order.
