Plan
Shape the change before any code exists. A prompt, GitHub issue or todo becomes review-sized tasks with visible context, and you approve the scope.
How planning works →From plan to merged pull request.
Every change takes the same path: a plan, an isolated run, a pull request, review, refinement, merge. Each stage leaves its record in GitHub and on the task, so anyone can read why the code looks the way it does.
Plan
Run
Review
Product path overview
Planscoped, visible context
Isolated runworktree + container
Pull requestsummary, cost, commits
Reviewscored findings
Refinecomments become commits
Mergeone click, like any PR
Four stages. One pull request.
Implement
Each task runs in its own Git worktree and Docker workspace, so parallel work never collides. The run ends as a pull request with its summary, commits, logs and cost. How a labelled issue becomes that pull request is covered step by step.
How isolated runs work →Review
Comment /review and get numbered merge blockers, suggestions and a score on the pull request. Ultrafix runs review and fix cycles toward your target score, within your cycle limit.
Refine
Ordinary pull request comments become follow-up commits on the same branch. /fix applies review findings, /merge brings the branch up to date, and you merge in GitHub.
Two ways to run without a per-task prompt.
Goals
Give the agent an objective and steer it while it works. ProPR commits each checkpoint to a draft pull request.
How goals work →Automations
Save a prompt once and get a Markdown report on demand, on a schedule, or from CI and chat.
How Automations work →