What problem does it solve? Large refactors often fail because they are attempted in one big change without a clear plan, scope agreement, or test strategy. This Skill structures the planning process by interviewing the developer, verifying assumptions against the actual codebase, and producing a refactor plan broken into tiny, safe commits filed as a GitHub issue. ## Core Features & Use Cases - Structured Interview Process: Gathers the problem statement, explores alternative solutions, and nails down exact implementation scope through detailed questioning. - Codebase Verification: Explores the repository to confirm the developer's assertions and checks existing test coverage for the affected area. - Tiny Commit Planning: Breaks the implementation into the smallest possible commits so the codebase stays in a working state after each step, following Martin Fowler's refactoring advice. - GitHub Issue Output: Files the final plan as a GitHub issue using a template covering problem statement, solution, commits, decision document, testing decisions, and out-of-scope items. - Use Case: A developer wants to migrate a legacy module to a new architecture. The Skill interviews them about goals and constraints, checks test coverage, then produces an RFC-style GitHub issue with a step-by-step commit plan. ## Quick Start Ask the assistant to help you plan a refactor of a specific module and file the resulting plan as a GitHub issue.