Split a larger prompt into changes ready for review.

Generate a plan

Start with the broader prompt and repository context. In planning, paste the full prompt and ask ProPR to identify the risky boundaries before implementation starts.

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 generated tasks until each one is small enough to review on its own. If the first plan still groups too much together, reply with a concrete split request.

Approve smaller pieces

Finalize the plan into smaller implementation items and choose the right agent or model for each piece. A good split is concrete enough that each approved task can become its own branch through isolated execution when that is safer for review or recovery.

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 can open its own PR and continue through the same PR review loop. Smaller PRs let reviewers check intent, isolate regressions, revert one risky piece, or ask ProPR for a focused follow-up without reopening the whole original prompt.