01 / Decide the outcome
Make the plan small enough to start.
A useful project plan makes the next decision easier. Start with one person, one problem, and one observable improvement. Give your AI coding assistant that destination before asking it to choose files, dependencies, or implementation details.
Name the change a person will notice
Write an outcome that can be demonstrated. "Improve settings" leaves too much room for interpretation. "Let a project owner change the default branch and see the saved value after refresh" gives the assistant a concrete finish line. Include the current behavior so it can distinguish a bug fix from a new feature.
Draw a useful boundary
List what belongs in this delivery and what can wait. A branch-setting task may include validation and a persistence check; it does not automatically include a settings redesign. Ask for an initial file map and a proposed sequence. Treat that sequence as a draft until you have checked the repository assumptions.
A starting prompt
Outcome: Project owners can save a default branch. First inspect the existing settings flow. Propose the smallest change and relevant checks. Do not edit files until the plan is reviewed.