request-refactor-plan

To create a stepwise refactor plan with tiny commits, this Skill conducts an interview to gather requirements and scope, then outputs a detailed plan mapped to a GitHub issue template. It defines commit-by-commit tasks and includes validation steps for test coverage.

Documenting RFC-driven refactors is best handled by an interview-driven requirement gathering process. This approach clarifies goals and constraints, preventing scope creep by recording the structured plan directly as a GitHub issue for clear hand-off to implementers.

You can turn an interview into a structured GitHub issue by describing your refactor goal and repository. The Skill interviews you to define scope and testing coverage, generating an issue-template-driven output with commit-by-commit tasks for implementation.

Yes, this interview-based planning approach checks test coverage as part of its validation steps. It ensures scope decisions are validated against test coverage before generating the final commit-by-commit tasks in the GitHub issue.

You can use this to plan refactors for any codebase undergoing RFC-driven changes. It does not require specific frameworks or dependencies, relying solely on an interview process to gather requirements and output a tiny-commit refactor plan.

Using an interview to generate a refactor plan prevents scope creep and ineffective commits by enforcing structured requirement gathering. It clarifies constraints upfront and produces an issue-template-driven output with small-commit granularity for a clear implementation hand-off.