request-refactor-plan

Plan a large refactor by interviewing stakeholders about the problem and scope, then breaking the work into tiny commits that each leave the codebase working. This Skill automates that process and files the result as a GitHub issue.

Break a refactor into small commits by following Martin Fowler's advice to make each step as small as possible so the program always works. The Skill generates a plain-English commit plan where every commit leaves the codebase in a working state.

A refactoring plan should include a problem statement, proposed solution, detailed commit plan, decision document covering modules and interfaces, testing decisions, and out-of-scope items. It should avoid specific file paths or code snippets that quickly become outdated.

Yes, the Skill inspects the codebase for existing test coverage of the affected area before planning. If coverage is insufficient, it asks the user about their testing plans and records testing decisions in the issue.

Skip the full interview process for trivial refactors like renames or small extractions that fit in a single commit. The detailed planning workflow is designed for substantial refactors where scope, decisions, and testing strategy need team alignment.