[Docs] Explain review capacity for parallel tasks - #1612
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
[Docs] Explain review capacity for parallel tasks#1612roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a concise operating pattern to the task-review guide for teams running Roomote tasks in parallel. The guidance covers independently reviewable outcomes, avoiding overlapping changes, clearing blocked work, and reviewing completed work before increasing concurrency.
Why this change was made
Parallel agent execution moves the bottleneck from producing changes to reviewing them. The docs described how to run and inspect tasks, but did not give teams a practical limit or workflow for keeping a growing task queue reviewable.
Impact
Teams now have a concrete review-capacity rule of thumb: optimize concurrency for the work they can verify, not the number of tasks Roomote can run.
Screenshots