What problem does it solve? Refactoring without a plan leads to oversized, risky changes that are hard to review and roll back. This Skill turns a vague refactoring idea into a structured, interview-driven plan broken into tiny, safe commits, then files it as a GitHub issue for team visibility. ## Core Features & Use Cases - Structured Interview Process: Walks through problem description, codebase verification, alternative options, scope definition, and test coverage checks before planning. - Tiny Commit Breakdown: Applies Martin Fowler's principle of making each refactoring step as small as possible so the codebase stays working after every commit. - GitHub Issue Output: Produces a complete refactor plan using a fixed template covering problem statement, solution, commits, decision document, 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, checks existing test coverage, then files a GitHub issue with a step-by-step commit plan the team can execute incrementally. ## Quick Start Ask the assistant to create a refactor plan for the module you want to restructure and answer its interview questions.
