At any pipeline stage, you can assign a ticket to an Xpert with an instruction. The Xpert carries out the work for that stage, posts its outcome and reasoning as a comment, and moves the ticket forward where the stage allows.
Each assignment creates a run: a recorded unit of work that captures the instruction, the Xpert's outcome, and how long it took. A ticket builds up a history of runs over its life, so you can see exactly what each Xpert was asked to do and what it produced.
Getting good results from Xpert runs
The instruction you give at assignment is the Xpert's only brief for that stage. A specific instruction gets a better result than a vague one. At Planning, something like, "write a retention plan for lapsed users in the 30–90 day window, push and email only" gives the Xpert relevant context to produce a useful first draft.
If the Xpert's output is not quite right, you can edit it yourself and move on, or reassign with a revised instruction, which starts a new run. There is no way to cancel a run in progress; if you need to change direction, wait for the current run to complete and then reassign.
What happens during a run
Once you assign a ticket to an Xpert with an instruction, the run is queued and starts as soon as a slot is available. You can see the run's status on the ticket (queued, running, waiting on approval, completed, or failed), and the stream updates as it progresses.
When the run completes, the Xpert posts a comment with its outcome and any reasoning. If the stage allows it, the ticket advances automatically. If the stage requires human action (Approved or Assembly) or the checklist is not fully passed (QA), the Xpert posts its comment and leaves the ticket in place for you to review and move.
If a run fails, a failed record and an explanatory comment are left on the ticket. The ticket stays in its current stage. You can address the issue and reassign to try again.
Stages Xperts can advance
Stage | Xpert can advance? |
|---|---|
Backlog | Yes |
Planning | Yes |
Content | Yes |
QA | Only when every checklist item passes or is marked not applicable; human must sign off to reach Approved |
Approved | No (human sign-off required to reach this stage) |
Assembly | No, human action required |
Runs on blocked tickets
If a ticket is blocked when you assign an Xpert, the run is queued but will not start until the block is cleared. This means you can queue work in advance: assign a run and then block the ticket to hold it until you are ready.