refactor-scope-session

Define scope boundaries by establishing clear in-scope and out-of-scope items before refactoring begins. Document what will change, what won't, and the constraints that guide the refactor. This prevents scope creep and ensures the team focuses on a single, measurable goal per session.

A refactor scope checklist includes goals, in-scope changes, out-of-scope constraints, success criteria, and behavior preservation rules. This functional framework captures what done looks like and ensures minimal risk by keeping the refactor focused and bounded.

One goal per session reduces risk and improves measurability. Smaller, focused refactors are safer, easier to test, and simpler to review. This principle ensures you can verify behavior is preserved and detect issues quickly if something breaks.

Behavior preservation is enforced through explicit success criteria and required tests defined in your scope plan. Document what behavior must not change, then validate it with test coverage before and after the refactor to confirm the system works as before.

Establish refactor scope before writing any code. Define boundaries, goals, and success criteria upfront to guide what will and won't change. This planning phase prevents mid-refactor scope creep and keeps the task focused and measurable from start to finish.