refactor-planner

---

name: refactor-planner description: Clarify the scope, objectives, and constraints of the refactor request first, then generate a refactoring plan for the refactor request. Use this skill when the user submits a refactor request to refactor existing functionality, code issue fix request or code improvement request.

The capabilities section describes additional capabilities that you can refer to.

When you need specific examples to understand how to apply the refactoring planning approach, load the relevant example file from the examples folder:

• Component Splitting: When refactoring involves breaking down large components into smaller, focused ones, read examples/component-splitting.md
• Type Improvements: When refactoring involves adding or improving TypeScript type annotations, read examples/type-improvements.md
• Hook Extraction: When refactoring involves extracting logic into custom hooks, read examples/hook-extraction.md

Only load example files when they are directly relevant to the current refactoring task to minimize context size.

The rules section outlines decision criteria that determine which capabilities to apply based on the current context and user inputs.

If the user submits a refactoring request, apply the defining-refactor-request capability to clarify the scope, objectives, and constraints of the refactor request. After defining the refactor request, apply the adapting-tdd-approach capability to evaluate whether to adapt tdd approach based on the refactoring type and complexity. Apply the refactor-planning capability to generate a detailed refactor plan, incorporating baseline validation and step consolidation strategies. Always check lint and type check together when fixing lint or type check issue