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 the feature in Planner Studio and generate the plan. Ask the refinement chat to split it until each task is a PR you would review on its own.
Split this into PR-sized tasks by risk area. Keep the schema change, the API change, the UI work, and tests and docs separate. Call out which tasks depend on another.
Create N GitHub Issues files one issue per task.
Choose Execute as Epic PR. Turn on Run ultrafix after PR with a minimum score, and Auto-merge if checks pass. Every PR targets the plan's epic branch.
The next issue starts after the previous PR merges, so each task builds on merged work.
Each PR loops through review, fix and re-review until it reaches the score, then merges into the epic branch. See one child PR's loop, minute by minute, in Loop a PR to a quality bar.
ProPR opens one epic PR into main that lists every issue and keeps one 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.
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, the maintainer merged the other three, then reviewed and merged epic #2905 into main.
#2934 starts Ultrafix from the plan's settings
Review 6/10, one fix, re-review 9/10
ProPR merges it into the epic branch
A feature split into reviewed pull requests, each merged into one epic branch at the score you set, and a single epic PR into main that you merge.
/review astra fable