Refactoring Plan Skill

Refactoring means improving structure without changing behavior — and the danger is doing it in one big risky sweep. This skill plans the opposite: a safety net first, then a sequence of small, behavior-preserving steps, each leaving the code green and committable. It separates refactoring from feature work, so you're never doing both at once.

Required Inputs

Ask for these only if they aren't already provided:

• The code & the pain — what's being refactored and why (hard to change, duplicated, slow, untestable).
• Test coverage — what tests exist around it (and the framework). If none, that's step zero.
• The goal — the target structure or what you want to make easy next (e.g. "so I can add payment provider #2").
• Constraints — what must not change (public API, behavior, performance), time budget.

Output Format

Refactoring plan: [target]