request-refactor-plan

Plan a code refactor with tiny commits by interviewing stakeholders to capture problem statements, define solution outlines, and break changes into a structured commit-by-commit sequence for a GitHub issue. This ensures safe, incremental refactoring with clear scope.

A GitHub issue template for a refactor proposal should include a Problem Statement, Solution outline, Commits plan, Decisions, and Testing sections. These sections formalize goals, constraints, and risk areas discovered during the planning interview.

Break down a large software refactor by guiding discovery through user interviews to surface goals and risks, then dividing the work into tiny commits with clear scope. Each commit represents a safe, incremental change suitable for tracking.

You need a guided interview to scope a refactoring project when you must surface hidden goals, constraints, and risk areas before coding. It verifies the current state and translates findings into a structured, commit-by-commit plan.

Yes, you can generate a commit-by-commit plan for a GitHub issue without manual outlining by using an automated interview process. It captures the problem statement and solution outline, then structures the sequence into tiny, actionable commits.

The best way to document refactor decisions and testing strategies in GitHub is to generate a structured issue template. It captures decisions made during the scoping interview and outlines specific testing steps alongside the tiny-commit plan.