What problem does it solve? Large refactors that touch many files often fail because changes are made in the wrong order, dependencies are missed, and there is no way to recover when something breaks. This Skill turns a refactoring goal into a structured, sequenced execution plan before any code is modified. ## Core Features & Use Cases - Dependency-Aware Sequencing: Orders changes safely — types and interfaces first, then implementations, then tests — so each step builds on a stable foundation. - Structured Output Template: Produces a Markdown plan with current state, target state, an affected-files table with dependency annotations, phased checklists, verification steps, a rollback plan, and a risk list. - Use Case: You need to rename a core domain model used across 40 files. The Skill searches the codebase, maps every affected file and its dependencies, and outputs a phase-by-phase checklist where each step includes a verification command and an undo path. ## Quick Start Ask the assistant to create a refactor plan for your change, for example: plan a refactor to extract the authentication logic from the user service into a standalone module.
