The product owner answers in the browser. The agents code on the developer's machine.
PRFactory puts the product owner and the developer in the same ticket. When an AI agent needs a decision, it writes clarifying questions and the ticket waits. The product owner answers them in the browser, from anywhere, and planning continues on the developer's machine with the answers in hand.
The problem
AI agents guess when a requirement is ambiguous, and a wrong guess costs more later than a question costs now. But the person who can answer is rarely the one at the terminal where the agent runs.
How PRFactory handles it
- Questions are a stop, not a chat. In phase 2 the agent writes numbered questions, and the ticket waits at awaiting answers. Planning cannot start until they are answered.
- Answer from the browser. The product owner, or anyone with access, answers on the ticket page. No terminal, no repository access, no agent installed.
- The coding happens elsewhere. Submitting the answers queues the plan draft, and the developer's worker picks it up and runs it locally with the answers in the prompt.
- Separate people, separate jobs. A person owns the ticket and answers its checkpoints; a machine executes it. Moving the ticket to another machine does not change who owns it.
- One history. Questions, answers, plan, approvals and who made them stay on the ticket for everyone to read.
◇ product ownerbrowser · anywhere
1. Should archived customers appear in the export?
No. Archived customers stay out of the export.
2. Which date marks a customer as archived?
The archived_at date on the customer record.
3. Is the export limited to the user's own region?
Enter your answer here...
◈ developer's machineatf · worktree
✓Ticket extracteddone
✓Questions written3 questions
⌛Waiting for answersno agent running
4Plan draftqueued on submit
Bring your product owner into the loop
Questions in the browser, agents on the machine, one ticket for both.