How PRFactory turns a ticket into a pull request
An automated pull request workflow with people in it. AI coding agents draft on your own machines, a second agent reviews the work, and you approve at the checkpoints that matter. Seven phases, each with one job.
The phases, step by step
PRD refinement (optional)
For a ticket that starts as a raw idea. An agent drafts a product spec and clarifying questions; the product owner answers them and approves the spec. Skippable.
Ticket extraction
The agent turns a ticket, written in PRFactory or imported from an issue tracker, into a structured requirement the later phases build on.
Clarifying questions and implementation plan
The agent writes numbered questions and the ticket waits. Anyone with access answers them in the browser. The agent then drafts a six-section plan that maps every acceptance criterion to a named test, and PRFactory checks it for completeness before anyone reads it.
Plan review
A different agent from the plan's author reviews it, and the two iterate until the reviewer approves or the round limit is reached. A project can switch this step off.
Test plan
The agent writes the test plan against the approved plan, red before green: each automated test is named and written to fail first.
Development
The agent implements the approved plan test-first, in a git worktree on the developer's machine. The developer reviews the diff.
AI code review
Cross-agent code review: the agent that wrote the code never reviews it. Reviewer and implementer iterate within a round limit. Works for .NET and any other language the agents read.
Visual QA
Only for tickets that touch the UI: an agent checks the rendered pages. A project can switch this step off.
Testing
The developer runs the tests and verifies the critical paths. An agent can interpret the results, but the sign-off is a person's.
Pull request and merge
PRFactory opens a pull request. Reviewers approve and merge it on GitHub, Bitbucket or Azure DevOps; agents never merge on their own.
Where you review and approve
Five of these checkpoints stop the ticket until a person acts: the answers, the plan, the test plan, the testing sign-off and the pull request. For a ticket that changes the UI, a person also approves the visual QA report. Reading the diff in phase 4 does not stop the ticket.
Answer the clarifying questions
The product owner, or anyone with access, answers in the browser. Planning cannot start before the answers are in.
Approve the implementation plan
Approve, or reject with a reason and the plan is revised. A failed completeness check can be overridden, and the override is recorded.
Approve the test plan
Sending it back re-runs only the test plan; the approved plan stays as it is.
Review the diff
The developer reads the change.
Sign off the testing
Automated and manual results are on the ticket; the decision to pass is the developer's.
Review and merge the pull request
The pull request is reviewed and merged by people, on your Git platform.
The server orchestrates. Your machines do the work.
PRFactory never runs an agent and never calls a model API.
The browser
- See every ticket's phase, agents and artefacts live
- Answer questions, approve, reject
- Choose which machine runs a ticket
PRFactory server
- Ticket state and phase transitions
- Plans, Q&A, reviews and other artefacts
- The work queue workers claim from
- Opens the pull request
- Runs no agent, calls no model API
AgentTeamForge worker (atf)
- Claims queued phases for its repositories
- Runs Claude Code, Codex and other CLI agents with your subscription
- Works in a local git worktree and pushes the branch
- Reports output and artefacts back
Run your next ticket through it
Connect the agents you already use. Keep every decision.