standup

To consolidate multiple git worktrees and pull requests into one merge plan, you can use a markdown-based standup room to gather input from all active branches. A facilitator moderates read-only rounds where participants share status and agree on a single target branch and merge order.

A markdown standup room for git collaboration is a shared, read-only chat environment defined by a single STANDUP.md file. It aggregates multiple git worktrees and open PRs, allowing teams to run moderated discussion rounds and converge on a unified consolidation plan without manual meetings.

To start a standup room to coordinate multi-branch work, open a shared markdown file with a specific goal and prompt, then invite participants to join. The facilitator runs discussion rounds, and the group agrees on outcomes before writing a final summation for execution.

You cannot execute changes directly within the standup markdown file, as it is strictly read-only for participants. Instead, the room produces a final summation that you execute separately using the /do command after the team agrees on the consolidation outcomes.

Yes, the standup collaboration room requires atomic locking for markdown writes to ensure data integrity during multi-participant collaboration. This prevents conflicting updates to the STANDUP.md file while participants post turns and the facilitator moderates the rounds.

A limitation of using a markdown file for multi-branch git coordination is that it remains strictly read-only, preventing direct commits during rounds. Additionally, the workflow depends on a single STANDUP.md file and a facilitator to manually guide the summation process.