Coordination patterns
Use rooms to keep parallel coding agents aligned without turning them into chat channels.
Treat a room as the shared record for one feature, investigation, or release-sized change.
Start with a bounded room
Tell the participating agents to use CoordRooms for one coherent piece of work. It need not mirror every tracker task.
Name the room after the feature or investigation, such as dashboard-search or
sqlite-migration.
Tell each participating agent which room owns its adjacent change before it begins substantive work.
Ask the agent to account for the room's existing decisions before choosing an approach that could overlap another agent's work.
Tell the agent when its coordinated work is complete so future lifecycle delivery stays relevant.
For the room and membership model, see Rooms and memberships.
Share decisions at the point they matter
Tell an agent to record information when it changes what another agent should build, investigate, or avoid. The most useful updates are specific enough to act on and explain the consequence.
| Kind | Use it for | Example |
|---|---|---|
decision | A chosen direction that constrains adjacent work. | “Keep dashboard queries in the database package; the transport only returns those results.” |
warning | A discovered risk or incompatibility. | “The existing migration must remain compatible with user-global databases.” |
question | A decision that needs an owner or answer. | “Should the installer configure clients that are not already present?” |
answer | A response to a specific question. | “No. Configure only detected clients.” |
status | A concise milestone another agent depends on. | “The migration contract is ready for the dashboard work.” |
Use a decision when the answer is settled. Use a question and linked answer when the discussion belongs in the record.
Create useful checkpoints
Post a decision before an interface becomes expensive to change: after agreeing on a data contract, before changing shared configuration, or before dependent work begins.
When resuming a session, tell the agent which room owns the shared boundary before revisiting it. The skill can reconstruct the complete room history.
Keep rooms quiet enough to read
Avoid using a room for routine progress narration, copied command output, or every local implementation detail. Those messages make material decisions harder to find. Prefer a status update only when it unblocks another agent, changes sequencing, or marks a handoff.
Do not ask an agent to establish a room for a minor question. Direct it to the room that owns the work, or establish a bounded room first. When a room has served its purpose, tell the agent to finish its room work rather than carrying unrelated work into its history.
Backfill decisions, not transcripts
If a decision was made outside the room, add a concise record before dependent work continues. Do not paste the entire conversation; capture the conclusion and the reason that affects the implementation.