What problem does it solve? Large refactors often fail because they lack a clear, incremental plan. 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 scope definition 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 Breakdown: Applies Martin Fowler's principle of making each refactoring step as small as possible so the codebase always stays in a working state. - GitHub Issue Template: Produces a standardized issue with Problem Statement, Solution, Commits, Decision Document, Testing Decisions, and Out of Scope sections. - Use Case: A developer wants to migrate a legacy module to a new architecture. The Skill interviews them about constraints, verifies assumptions against the actual codebase, and files a step-by-step refactor plan as a GitHub issue the team can execute incrementally. ## Quick Start Ask the assistant to create a refactor plan for the module you want to change and file it as a GitHub issue.
