request-refactor-plan

A codebase refactor plan converts vague ideas into a detailed, auditable document via user interviews. It collects scope, constraints, and success criteria from stakeholders to ensure safe incremental changes across projects.

To create a GitHub issue for a refactor, an automated skill conducts a user interview to define scope and constraints. It then generates and files a GitHub issue containing tiny-commit sequences and PR templates to guide implementation.

Yes, you can use tiny commits to plan an RFC for complex changes. The planning process breaks down refactors into small, verifiable steps with clear rollback guidance, generating formal RFC documents and GitHub issues to guide implementation.

The best way to document a refactor plan is an interview-driven approach that captures stakeholder constraints and success criteria. It produces a formal plan document filed as a GitHub issue, ensuring the refactor is auditable and easy to track.

Planning a codebase refactor uses user interviews to accurately define scope and constraints. This interview-driven planning collects success criteria from stakeholders before generating a GitHub issue with tiny commits, ensuring the refactor meets project goals.