request-refactor-plan

Plan a safe code refactor by interviewing stakeholders to define scope, assessing test coverage, and breaking the work into tiny, testable commits. This approach mitigates risk and generates a structured GitHub issue to track incremental changes.

Writing an RFC for a complex software migration involves gathering user goals, identifying test gaps, and structuring the plan into incremental steps. This ensures risk management and produces an actionable issue with clear acceptance criteria.

Breaking down a large refactor involves conducting user interviews to define constraints and mapping the work into the smallest possible testable steps. This creates a structured roadmap that ensures reliability through incremental commits.

You can generate a GitHub issue for tracking an incremental migration by defining the refactor scope and risk considerations. The issue includes rationale, acceptance criteria, and a tiny-commit roadmap to guide the structured work.

Tiny commits ensure that each step of a complex refactoring is testable and independently verifiable, reducing overall risk. This method allows teams to manage test coverage gaps and maintain reliability during incremental migrations.

Planning an incremental refactor without stakeholder interviews limits the ability to accurately define scope and user constraints. Skipping this step risks missing critical test coverage gaps and producing an incomplete migration plan.