pair-relay

Pair-programming for large-scale software development is managed by splitting roles between a Navigator for planning and a Driver for implementation. This division prevents overburdening a single agent and maintains seamless progress.

Handling complex implementations across multiple layers requires a Navigator and Driver pair-workflow. This approach manages multi-language tasks, such as Rust and Python integration, by separating planning review from actual implementation.

To start a pair-programming workflow for code review and task division, invoke the pair-relay command. This initiates the role separation, requiring planning review and adjustment before implementation begins.

Yes, planning adjustment is required before implementation in a pair-workflow. The Navigator role handles the initial planning and review phase, ensuring the Driver has a validated structure before beginning complex task execution.

Yes, you can maintain consistent documentation while splitting tasks between Navigator and Driver. The pair-workflow explicitly supports collaboration on planning adjustments and document management throughout the implementation process.