Split a larger prompt into changes ready for review.

Planning turns a broad prompt into issue-sized tasks, each with its own focused PR. Take this path when the context preview is large or the change spans several areas.

Describe
Run isolated
Review in GitHub

Feature overview

You start with
A broad prompt that spans several areas
You use
Planning · Isolated execution
Takes
One planning pass, then a PR per task

Generate a plan

Paste the full prompt into planning and ask ProPR to find the risky boundaries before any code is written.

Plan this change before writing code:

Add team billing settings to the app. Admins need to store billing contact details, update the subscription plan through the API, see the current plan in the account settings UI, and get tests/docs for the new workflow.

Please inspect the repository and propose the smallest reviewable tasks. Do not implement until I approve the split.

Refine task boundaries

Adjust the tasks until each one reviews on its own. If the first plan bundles too much, ask for a concrete split.

Please split this into separate PR-sized tasks by risk area. Keep schema changes, API behavior, UI work, and tests/docs separate where possible. Call out task dependencies and which items should run on their own branch.

The team billing plan split into four tasks, one tab each: billing fields, billing API, billing section, and tests and docs

Approve smaller pieces

Finalize the plan and pick the agent or model for each piece. Each approved task gets its own branch through isolated execution.

Expected task split:

1. Schema change
   - Add billing_contact_name, billing_contact_email, and plan_id fields.
   - Include migration, rollback notes, and model validation tests.

2. API change
   - Add account billing endpoints for reading and updating the plan.
   - Enforce admin-only access and cover authorization failures.

3. UI change
   - Add the billing settings section to account settings.
   - Show current plan, contact fields, save states, and API errors.

4. Tests and docs
   - Add integration coverage for the full billing update flow.
   - Document setup, permissions, and manual verification steps.

Review linked PRs

Each task opens its own PR and goes through the same PR review loop. Small PRs let reviewers check intent, isolate regressions, revert one risky piece, or request a focused follow-up without reopening the whole prompt.

The billing plan executing as individual tasks: each issue has its own pull request, one in review, one refining, one running and one pending, each on its own model

What you get

Several focused PRs, each on its own branch with its own review, in place of one sprawling diff.

Planning → All playbooks