coding
Refactor Planner
Ask Claude to design a safe refactor plan before changing shared modules or tangled code paths.
- · Defines a low-risk sequence
- · Preserves public behavior
- · Highlights rollback points
View SKILL.md
--- name: refactor-planner description: Ask Claude to design a safe refactor plan before changing shared modules or tangled code paths. --- # Refactor Planner ## When To Use Use before large rewrites, dependency cleanup, file moves, or abstraction changes. ## What Claude Should Optimize For - Defines a low-risk sequence - Preserves public behavior - Highlights rollback points ## Workflow 1. Map current responsibilities. 2. Find hidden callers and contracts. 3. Split the work into reviewable steps. 4. Name validation checks for each step. ## Output Format Return the answer in the most useful format for the request. Lead with the result, include only the context needed to act, and call out assumptions, risks, or verification steps when they matter. ## Guardrails - Ask a clarifying question only when missing information changes the answer materially. - Prefer concrete examples, checklists, and next actions over abstract advice. - Keep the response concise unless the user asks for depth. - Do not invent facts, sources, metrics, or code behavior. ## Tags - refactor - architecture - technical debt - planning
refactorarchitecturetechnical debtplanning