Human approval
What approving a plan means, what it does not mean and how the gate is recorded from the CLI.
The approval gate
When the Spec Author finishes, the Work Item is left in ready. That state is not a technical waiting room: it is the point where the person reviews the planning and decides whether it is implemented or not. No Work Item moves from ready to in_progress without an explicit human decision.
The gate exists because responsibility for what gets built does not belong to the agent. The Leader coordinates and the Spec Author proposes, but agreement on scope, design decisions and requirements belongs to whoever commissions the work.
What approving means
Approving is not reviewing code: there is none yet. It means confirming that the planning reflects the agreement reached and that the decisions that determine the result are correct.
- That the requirements describe the behavior you expect.
- That the design decisions and the discarded alternatives make sense.
- That the tasks cover the scope and make clear how it will be verified.
- That what is left out of scope is also what was agreed.
Approving is an act of responsibility, not an automatic green light. If the planning does not reflect what was discussed, the right step is to ask for changes, not to approve and fix it later.
What approving does not mean
- Silence does not approve, and neither does an ambiguous answer. Without an unambiguous confirmation, the Work Item stays in ready.
- Opening the viewer does not approve:
rei viewis read-only and has no approval button or route. - Reading the planning does not approve: the decision is communicated and recorded, not inferred.
- Approving does not block future changes: if the implementation drifts, the Reviewer can reject it.
How it is recorded from the CLI
Approval is given in the chat or in the terminal. The Leader records the state change; the person does not need to run anything, although they can if they work directly with the CLI.
rei status set 2026-10-27_01-54__mi-feature in_progressOn approval, the Leader also records the commit at which implementation starts in base_commit. If the GitHub Issues integration is active and the Work Item is a Feature, the issue + branch gate is resolved at this same moment, before the state is moved.
If you do not approve
If something does not reflect what was agreed, or a design decision does not convince you, say so in natural language. The Leader relaunches the Spec Author, the planning is updated and presented again. The Work Item does not move to implementation in the meantime.
Rejection in review is a different moment: if the Reviewer finds that the implementation does not meet the planning, the Work Item moves to changes_requested and returns to in_progress with the corrections. You do not have to manage that loop: the Leader coordinates it.
Next step
If you want to see the gate in a real cycle, start with the tutorial. If you already work with Work Items, the GitHub Issues guide explains how the gate coexists with the issue and the branch.
A human sign-off releases the sheet. Silence is not approval.