Work items

Work items live on a board, so you can see what's planned, what's underway, and what's finished. Each one is a plain-language description of a change to make. You write down what you want, someone makes that change in Aprimo, and the resulting change set gets linked back to the work item so there's a clear record of what was built and why.

An AI agent can do that work too, if you want it to. AI access starts off, and letting an agent propose changes is a separate choice from letting it read. See Give an AI agent access.

What's on a work item

• A number and title. Every work item gets a stable number like #12, so you can refer to it anywhere.
• Details. The requirement or user story, in plain language, enough for someone to do the work.
• Acceptance criteria. A checklist of what's true once the work is done, for example “a content type named Car exists” or “the VIN field is required.” Check them off as they're met.
• Linked change sets. The change sets that deliver this work, so you can trace a requirement to the configuration that fulfilled it.

Acceptance criteria

Acceptance criteria are the checkable definition of done. They turn a vague request into something anyone can verify. Keep each one short and checkable, one condition per line. A person or an AI agent can build against them, and a reviewer can tick them off one by one.

The board

Work items sit in columns you define (To do, In progress, Done, or whatever suits your team). Drag a card to move it, or let it move itself: when a change set is linked to a work item, Mochi can advance the card as that change progresses. See the glossary for the terms used on the board.

Linking work to a change set

There are two ways to link a work item to the change set that delivers it:

1. Mention its number. Put #12 in a change set's description and Mochi links work item 12 automatically.
2. Pick it explicitly. On a change set, choose Edit next to Work items and select the ones it fulfills.