[Docs] Explain review capacity for parallel tasks

apps/docs/tasks.mdx

@@ -142,6 +142,22 @@ If verification is missing, ask Roomote to run the specific command or explain
 why it cannot. If the task touched user-facing behavior, inspect the preview,
 screenshots, or product surface before shipping.
 
+## Keep parallel work reviewable
+
+Running more tasks only helps when the team can still review their results.
+Use the task board as a review queue, not just a launch queue:
+
+1. Give each task one outcome that a reviewer can accept or reject on its own.
+2. Avoid starting tasks that change the same files or depend on an unmerged
+   branch unless the prompts explain that dependency.
+3. Keep **Needs input** and **Blocked / failed** clear before launching another
+   batch, so unfinished work does not disappear behind new tasks.
+4. Review the evidence and merge or reject completed work before increasing
+   concurrency.
+
+If the review pile keeps growing, reduce the number of active tasks. The useful
+limit is the number your team can verify, not the number Roomote can run.
+
 ## Multi-person tasks
 
 Different teammates can run separate tasks in parallel. Teammates can also