Bring your ideas to one agent
The developer has tried an app feature and found its main screen confusing. They describe the problem to product-lead@factory, their point of contact, without first finding the agent responsible for the interface.
What happens
Clarify the desired change
The lead asks whether essential controls should stay on the main screen while advanced settings move elsewhere. The developer confirms that the starting point should be obvious and advanced settings must remain available.
Record the decision
The lead saves that direction in DECISIONS.md. This preserves the developer’s choice as project material the team can consult.
Route the work
The lead creates setup-001 for dev-ui@factory, including both the requested change and a follow-up with the human. dev-ui@factory reads and claims it.
Keep the human conversation simple
The lead reports that the right teammate has the assignment and that the revised screen will come back for review. The developer did not need to locate the specialist, relay the discussion or track down the handoff.
What OpenRig does
OpenRig gives the lead a named teammate to route work to and a queue task for the resulting assignment. The task carries the clarified request into the specialist’s separate terminal.
What Claude or Codex does
The lead agent understands the feedback, asks the clarifying question, chooses the recipient and writes the task. The interface agent does the implementation. Saving the decision is ordinary file work by the harness.
When this helps
You can keep bringing ideas and feedback to one agent while a larger team works behind it. The lead handles the routing; you stay involved where your intent and assessment matter.