Running tickets
Label an issue ready and follow it from triage to production.
Start
Add the ready label to an issue in the project's repository:
gh issue edit 42 --add-label readyThe coordinator starts a run, labels the issue appli:working, and keeps one status comment on the issue up to date. The project's Runs board shows the ticket moving through the stations live.
Follow
Every station leaves its output on GitHub:
| Station | Output |
|---|---|
| Triage | A comment with a summary and acceptance criteria; type:* and size:* labels |
| Plan | A comment with the approach, files, test plan, and risk; a risk:* label |
| Implement | A pull request from the ticket's branch; the appli/checks status |
| Review | A review with inline comments; the appli/review status |
| QA | The appli/qa check run with each criterion's result, and a comment with screenshots of the preview |
Each agent runs as a thread in T3 Code on the worker; open it to watch or take over.
Approve
When review and QA pass, the status comment asks for your approval. Approve the pull request on GitHub. The coordinator merges it, pinned to the commit QA tested, and waits until production runs the merge commit. The issue ends with appli:done.
High-risk plans stop earlier: comment /approve on the issue to let implementation start.
Retries and stops
- Failed checks, a failed review, or failed QA send the ticket back to implementation once, with the reasons. After that the run stops with
appli:failedand says why. - Close the pull request or the issue to stop a run at any point; it ends with
appli:cancelled. - Label the issue
readyagain to start a new attempt. The board shows the latest attempt per ticket.