Reference · States

States

The seven workflow states, their transitions, the single in_progress limit and --force.

seven states · transitions · a single in_progress

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.

StateMeaningKind
pendingWork Item created, waiting for planning.Cycle
readyPlanning finished, waiting for human approval.Cycle
in_progressImplementation under way. Only one at a time.Cycle
reviewImplementation finished, waiting for review.Cycle
doneCompleted and approved; terminal state.Terminal
blockedThe work cannot continue.Branch
changes_requestedThe 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.

FromToTypeWhen
pendingreadyCycleThe Spec Author finishes the planning.
readyin_progressCycleRequires explicit human approval.
in_progressreviewCycleThe Implementer closes with its report.
reviewdoneCycleFavorable verdict from the Reviewer.
reviewchanges_requestedBranchThe Reviewer rejects the implementation.
changes_requestedin_progressBranchThe Implementer applies the corrections.
pendingblockedBranchThe work cannot continue.
readyblockedBranchThe work cannot continue.
in_progressblockedBranchThe work cannot continue.
reviewblockedBranchThe work cannot continue.
changes_requestedblockedBranchThe work cannot continue.
doneblockedForced (--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_progress rejects activating a second Work Item, also with --force.
  • rei check, rei doctor and rei items status fail if they detect more than one.
  • rei items status marks 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.

Forced transition
rei status set <work-item-id> blocked --force

The 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_commit so the next review sees only what changed.

Planning approval

Pending

A human sign-off releases the sheet. Silence is not approval.

Approval is recorded from the CLI; the viewer does not replace it.