What problem does it solve? Refactoring without a plan often leads to oversized, risky changes that break the codebase. This Skill turns a vague refactoring idea into a structured, interview-driven plan broken into tiny safe commits, documented as a GitHub issue. ## Core Features & Use Cases - Structured User Interview: Walks the user through problem description, alternatives considered, implementation scope, and testing strategy before writing anything. - Codebase Verification: Explores the repository to validate the user's claims and checks existing test coverage of the affected area. - Incremental Commit Plan: Breaks the refactor into the smallest possible commits following Martin Fowler's principle that the codebase stays working after every step. - GitHub Issue Output: Files the final plan as a GitHub issue using a fixed template covering problem, solution, commits, decision record, testing decisions, and out-of-scope items. - Use Case: A developer wants to split a monolithic service into modules. The Skill interviews them about scope and constraints, inspects the code, then produces a GitHub issue with a step-by-step commit plan. ## Quick Start Ask the assistant to create a refactoring plan for the module you want to change and file it as a GitHub issue.
