request-refactor-plan

To plan a refactoring project effectively, conduct a detailed interview to understand the problem, verify repository context, evaluate alternatives, define scope, and break the implementation into small, verifiable increments for safer execution.

The best way to break down a refactoring task is by splitting it into tiny, verifiable working increments. This structured planning process ensures safer implementation and easier verification during codebase maintenance.

Verify repository context by validating the repository's current state against initial assumptions. This refactoring planning process confirms or corrects codebase assumptions before defining the scope and implementation increments.

Yes, you should evaluate alternative refactoring approaches before defining the project scope. This planning process involves discussing alternatives to the proposed solution, ensuring the best approach is chosen before breaking down the implementation.

Create a durable issue for a refactoring implementation plan by using Beads after breaking down the project into small increments. This generates a comprehensive, durable issue ready for collaborative project management and execution.