code-refactoring

Yes, refactoring planning applies to Java, Node.js, TypeScript, and Python projects, especially monoliths and large classes requiring restructuring. It enforces external-interface stability while detailing risk assessments and safe migration steps for each environment.

To generate refactoring tasks, you provide a refactoring scope, such as a target module or class. The Skill then decomposes the work into an OpenSpec-style task list, detailing safe migration steps, risk assessments, and rollback strategies without executing any code changes.

A behavior-preservation contract is a formal agreement ensuring external-interface stability during refactoring. It maps dependencies, details rollback strategies, and outlines safe migration steps to guarantee the codebase behavior remains unchanged throughout the restructuring.

This planning approach outputs documentation and task lists only, deliberately avoiding executing any code changes. It provides a rigorous, behavior-preserving plan with dependency maps and rollback strategies that developers must implement manually or through separate orchestration.

To plan a behavior-preserving refactor, you define a formal contract ensuring external-interface stability, generate dependency maps, and produce actionable migration tasks. This Skill outputs a refactoring-plan.md and tasks.md detailing safe rollback strategies.

A refactoring plan yields two deliverables: refactoring-plan.md and tasks.md. These files contain the formal behavior-preservation contract, dependency maps, risk assessments, rollback strategies, and an OpenSpec-style task decomposition ready for orchestration.