request-refactor-planlisted

# Request Refactor Plan This is a side-route skill for work that is primarily about restructuring code safely rather than shaping a new feature. ## Invocation Position Use `/request-refactor-plan` when the user wants a refactor RFC, a tiny-commit migration path, or a safer way to reorganize code without jumping straight into implementation. Do not use it when the work is still a product-shaping problem for `/write-a-prd`, or when the refactor task is already concrete enough to execute directly in `/execute`. This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary. 1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions. 2. Explore the repo to verify their assertions and understand the current state of the codebase. 3. Ask whether they have considered other options, and present other options to them. 4. Interview the user about the implementation. Be extremely detailed and thorough. 5. Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change. 6. Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are. 7. Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as sm