Give work an owner
The developer asks product-lead@factory to start the next feature. The lead assigns it to dev-app@factory and records what the implementation should include.
What happens
Create the assignment
product-lead@factory creates feature-001 with rig queue. The task names its recipient, describes the feature work and asks for progress and remaining checks to be recorded.
Read before claiming
dev-app@factory receives a notification, then reads the full task. The notification is a prompt to check the assignment. The separate claim changes the task from pending to in-progress.
Confirm the pickup
dev-app@factory sends a short message back to say that it has claimed feature-001 and started. The message is useful conversation; the queue task is the record the lead can inspect later.
What OpenRig does
OpenRig keeps the task’s identity, destination and state available beyond the immediate exchange. The same feature-001 is visible at creation, reading, claiming and confirmation.
What Claude or Codex does
The lead chooses the recipient and writes the assignment. The receiving coding agent understands the task and does the implementation. Creating or claiming the task does not itself write the feature.
When this helps
Use a queue task when somebody is responsible for doing work. It gives later questions such as “Who has this?” and “Has it started?” something concrete to refer to.