States
The seven workflow states, their transitions, the single in_progress limit and --force.
The seven states
Every Work Item, whether Feature or Task, goes through the same states. Five form the linear cycle and two are branches outside it.
| State | Meaning | Kind |
|---|---|---|
| pending | Work Item created, waiting for planning. | Cycle |
| ready | Planning finished, waiting for human approval. | Cycle |
| in_progress | Implementation under way. Only one at a time. | Cycle |
| review | Implementation finished, waiting for review. | Cycle |
| done | Completed and approved; terminal state. | Terminal |
| blocked | The work cannot continue. | Branch |
| changes_requested | The review rejected the implementation and asks for changes. | Branch |
Transitions
The table is generated from the harness's canonical data. Exits to blocked are derived from all non-terminal states; done can only be left with a forced transition.
| From | To | Type | When |
|---|---|---|---|
| pending | ready | Cycle | The Spec Author finishes the planning. |
| ready | in_progress | Cycle | Requires explicit human approval. |
| in_progress | review | Cycle | The Implementer closes with its report. |
| review | done | Cycle | Favorable verdict from the Reviewer. |
| review | changes_requested | Branch | The Reviewer rejects the implementation. |
| changes_requested | in_progress | Branch | The Implementer applies the corrections. |
| pending | blocked | Branch | The work cannot continue. |
| ready | blocked | Branch | The work cannot continue. |
| in_progress | blocked | Branch | The work cannot continue. |
| review | blocked | Branch | The work cannot continue. |
| changes_requested | blocked | Branch | The work cannot continue. |
| done | blocked | Forced (--force) | Non-standard transition: requires --force and an explicit order. |
A single in_progress
The limit is hard: only one Work Item can exist in in_progress. It is not a style recommendation or a convention the agent can skip.
rei status set <id> in_progressrejects activating a second Work Item, also with--force.rei check,rei doctorandrei items statusfail if they detect more than one.rei items statusmarks the active Work Item with << ACTIVO and names the ones involved when there is a conflict.- Before starting another one, the active one must be closed (review or done), blocked or sent to review.
done is terminal
done closes the Work Item: it is not left through a standard transition. The only exit is done → blocked with --force, reserved for a non-standard transition with an explicit order from the user.
rei status set <work-item-id> blocked --forceThe branches
blocked and changes_requested describe stopped work, not success states. The Work Item keeps existing and keeps its planning and history.
- blocked is reached from any non-terminal state when the work cannot continue; it is left once the cause is resolved.
- changes_requested is produced by a Reviewer rejection in review. The Work Item returns to in_progress with the requested corrections.
- In changes_requested, the Reviewer records
last_review_commitso the next review sees only what changed.
A human sign-off releases the sheet. Silence is not approval.