Status Label State Machine
How labels transition in todo→doing→review→done order, and the rules for who can change them
The four skills export-backlog → implement-backlog → review-issue → merge-issue use
labels attached to GitLab/GitHub Issues (status labels) as a shared state machine—a mechanism where states change in a fixed sequence.
Which skill can trigger each transition is defined per transition.
| Transition | Skill that changes the label | When |
|---|---|---|
todo → doing |
implement-backlog |
When implementation starts |
doing → review |
implement-backlog / review-issue |
implement-backlog advances to review at most, once implementation is complete. review-issue does so when all blockers reach zero and a PR/MR (a submission requesting a code change review) is created |
review → blocked |
review-issue |
When the auto-fix loop hits its retry limit without resolving the issue |
review → done |
merge-issue only |
Only when the PR/MR is actually merged |