request-refactor-plan

Interview-driven planning decomposes the refactor into the tiniest possible commits, each leaving the codebase in a working state. The approach follows Martin Fowler's advice to make each refactoring step as small as possible so the program always works.

The Skill interviews you about the problem, solution, scope, and testing, then files a GitHub issue using a structured template. The template includes problem statement, solution, commit plan, decision document, testing decisions, and out-of-scope items.

Yes, the workflow inspects the codebase for existing test coverage of the affected area. If coverage is insufficient, it asks the user about their testing plans before finalizing the commit breakdown.

Skip it for trivial changes or single-file fixes where a full decision document adds overhead. The process is designed for substantial refactors that benefit from documented scope, architectural decisions, and incremental commit sequencing.

The template contains a problem statement, solution, a detailed plain-English commit plan, a decision document covering modules and architectural choices, testing decisions, and an out-of-scope section. It deliberately excludes specific file paths and code snippets that quickly become outdated.