Plan an epic and let it land.

Approve the plan once. ProPR files one issue per task, runs them in order, and carries each pull request through review into an epic branch. You review and merge one epic PR into main.

Describe

Run isolated

Review in GitHub

You start with: A feature too big for one pull request
You use: Planner Studio · Execute as Epic PR · Ultrafix · auto-merge
Takes: 16 issues in about 18 hours on the real run; most PRs merged within an hour of opening
Real run: propr #2905 (epic)

Generate and approve the plan

Describe the feature in Planner Studio. Edit the tasks or reshape them in the refinement chat until each one is a PR you would review.

Create N GitHub Issues files one issue per task.

A generated plan broken into five ordered tasks, each a future GitHub issue, with drag handles to reorder them — Each task in the outline becomes one GitHub issue.

Run it as an epic

Choose Execute as Epic PR. Turn on Run ultrafix after PR with a minimum score, and Auto-merge if checks pass.

Every issue gets the auto-merge label, and every PR targets the plan's epic branch.

Execution settings for every task in the plan: agent and model, Ultrafix with a minimum review score of 8/10 and a loop limit, and auto-merge — Ultrafix to 8/10 and auto-merge, applied to every issue in the plan.

Issues run one after another

The queue starts the first issue. The next one starts only after the previous PR merges, so each task builds on merged work. On the real run, every PR targeted 2888-epic-task-assignment-1m4.

Ultrafix carries each PR to the goal

Each PR loops through review, fix, and re-review until it reaches the score. ProPR then checks the repository's auto-merge policy and arms GitHub auto-merge into the epic branch. If the repository disallows auto-merge, or the PR has no CI, ProPR merges it directly once the same gates pass. When the policy declines, for example on a protected path, ProPR comments on the PR and the queue waits until you merge it.

The Ultrafix playbook walks through one loop.

You merge the epic PR

ProPR opens one epic PR into main that lists every issue, and keeps a single progress comment current as child PRs merge. When the last one lands, it posts Epic ready for final merge.

Review the whole feature there. /merge brings in the latest main, /review reads the combined diff, and you press merge.

@integrycommented on propr #2905

/review astra fable

One plan, sixteen merged pull requests.

The task-assignment plan on public integry/propr became issues #2888 to #2903. Claude Opus 5.5 implemented each one. All sixteen PRs ran Ultrafix and finished at 8/10 or higher; eleven started at 6/10. ProPR merged thirteen into the epic branch, and the maintainer merged the other three. The maintainer then reviewed, refined, and merged epic #2905 into main.

Sixteen PRs into one branch, one merge into main.Public propr #2905, shortened: the plan's queue in ProPR, child PR #2934 through Ultrafix into the epic branch, then the epic PR to its merge. The progress comment, the ready notice and the merge confirmation are staged in ProPR's current format; no public PR carries them yet.