ready-rock-quartet

You coordinate multiple AI agents by launching four role-locked sessions with explicit ownership (Lead, Reviewer, Breaker, Verifier) and a shared comms surface for monitoring progress and preventing drift during synchronous sprint work.

Role-locking assigns explicit responsibilities to specific agents, such as Lead, Reviewer, Breaker, and Verifier. You need it for multi-agent coordination tasks requiring clear ownership boundaries to prevent drift and ensure deterministic sprint execution.

To launch a four-agent sprint, start four named terminal sessions for the required roles, apply deterministic boot steps, and publish the sprint execution artifact before initiating any risky work to enforce governance and traceability.

Yes, a sprint-pattern approach suits tasks requiring explicit role ownership. It applies locked session names and a shared comms surface to coordinate four live agents, ensuring clear responsibility for artifact publication and execution.

Visible-terminal multi-agent coordination requires clear role prompts and deterministic boot steps. Without strict artifact publication and a shared comms surface, agents may drift, making it unsuitable for tasks lacking explicit role ownership boundaries.