What problem does it solve? Refactoring without a plan leads to oversized, risky changes that are hard to review and revert. 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 User Interview: Walks through problem description, alternative solutions, implementation details, and exact scope before writing anything. - Test Coverage Check: Inspects the codebase for existing test coverage of the affected area and prompts for a testing strategy if coverage is insufficient. - Tiny Commit Planning: Breaks the refactor into the smallest possible commits so the codebase stays in a working state after every step, following Martin Fowler's incremental refactoring advice. - GitHub Issue Output: Files the final plan as a GitHub issue 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 module. The Skill interviews them about scope and constraints, verifies the codebase state, and produces a GitHub issue with a 15-commit incremental plan the team can review and execute. ## Quick Start Ask the assistant to plan a refactor of a specific module and file it as a GitHub issue with tiny incremental commits.
