workflow-team

Parallel development coordination is managed by enforcing a Plan-Execute-Review workflow with clear file ownership rules. This prevents conflicts by defining roles, requiring plan approval, and staging execution from plan to merge.

Autonomous team workflows are structured through a phase-driven process encompassing Plan, Execute, Review, and Merge stages. This approach supports planning modes and spawn prompts to define a safe merge strategy with approved task completion and rollback notes.

The Plan-Execute-Review workflow handles delegation using Shift+Tab Delegate Mode and guided prompts. You start in lead mode to plan, spawn teammates, and monitor progress throughout the staged execution.

Yes, this workflow is specifically applicable to projects where multiple teammates work on the same feature branch. It requires defined roles, plan approval, and staged execution to ensure safe, auditable changes.

File ownership rules prevent merge conflicts by assigning clear ownership boundaries before execution begins. This ensures autonomous agents deliver features in parallel without overwriting each other's changes on the same branch.

A defined merge strategy is needed when coordinating multiple agents working on the same feature branch to ensure safe, auditable changes. It enforces approved task completion and provides rollback notes before final integration.