2026-08-30
Ready for Review is the product
Takeaways
- The bottleneck moved from writing code to reviewing it.
- In Progress and Ready for Review sit in the backlog. There is no Current panel.
- Reject with comments. The same story comes back.
Agents made writing cheap. Review is the job now. You can feel it in the PR list and in the standup that cannot name what is waiting.
When review lives in a pull request, a Slack thread, and a ticket that does not match, nobody can say what was accepted. The agent shipped. The story is missing.
The gate is on the list
In Beck, In Progress and Ready for Review sit in the backlog. There is no separate Current panel. Finish submits. Accept or reject with comments. Completed is the accepted pile.
The agent logs what it attempted, what succeeded, what failed, and its questions. That stays on the story. A reject is how scope dies — the same object comes back, not a new ticket that forgets the last attempt.
Linear’s answer for the agent era is diffs inside Linear. That is a real product if you want code review in the tracker. We do not have in-app pull request review. We will not pretend we do. You paste a branch and a PR URL on the epic if you want the link next to the work. Code review stays in your host. Beck holds whether the story is done.
Why this is the product
A prioritized list without a QA gate is a todo app. A coding agent without a gate invents “done.” Ready for Review is the sentence the team can say out loud.
Default autonomy is human review. The task loop and autonomy are the operational pages. The backlog is the picture.
You accept the work. That is the product.
Questions
Where does code review happen?
In your host (GitHub, and so on). Beck holds whether the story is accepted. You can paste a PR URL on the epic.
What if I reject?
Comments stay on the story. The agent iterates on the same object. Scope does not leak into a new ticket.
Can an agent accept its own work?
Only if you set autonomy to peer_review or full. Default is human_review.