Refactor Planning

Process

1. Understand Problem

• Get detailed description from user
• Ask about potential solutions they've considered
• Explore codebase to verify current state

2. Define Scope

• Interview user about implementation details
• Present alternative approaches — each approach as an option with trade-offs in description; use preview to show code sketches when applicable. Use AskUserQuestion when available; otherwise present as a numbered list.
• Define exactly what changes and what stays
• Check test coverage in affected areas

3. Break Down Work

Apply Martin Fowler's principle: "Make each refactoring step as small as possible, so that you can always see the program working."