request-refactor-plan

Plan safe refactors into tiny commits via structured user interviews.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/RemseyMailjard/superpowers --skill request-refactor-plan-remseymailjard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/RemseyMailjard/superpowers/tree/main/.github/skills/request-refactor-plan
Command: npx skills add https://github.com/RemseyMailjard/superpowers --skill request-refactor-plan-remseymailjard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to plan and document safe refactors through a structured interview-driven process, generating a tiny-commit plan and RFC-ready GitHub issue.

Core Features & Use Cases

  • Interview-driven scoping to capture the problem, potential solutions, and acceptance criteria.
  • Incremental planning that breaks refactors into the smallest possible commits for safe, testable changes.
  • RFC generation that creates a ready-to-file GitHub issue with a clear problem statement, proposed changes, and testing considerations.
  • Use Case: When faced with a major code restructuring, this skill produces a concrete, auditable plan to guide the team.

Quick Start

Describe the user's refactor goal and run a guided interview to extract requirements and generate a tiny-commit plan.

Frequently Asked Questions about request-refactor-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a safe code refactor with incremental commits?

To plan a safe code refactor, this Skill conducts a structured user interview to capture scope and acceptance criteria, then generates a detailed commit-by-commit plan ensuring each change is tiny, testable, and auditable.

What is the best way to write an RFC for a major code restructuring?

The best way to write an RFC for restructuring is using an interview-driven approach to extract problem statements and proposed changes, which automatically generates an issue-ready RFC template with clear testing considerations.

How does an interview-driven scoping process work for software refactoring?

Interview-driven scoping works by guiding you through targeted questions about your software refactor goal, extracting requirements and potential solutions to produce a structured, incremental plan before any code changes.

Can I generate a GitHub issue template for my software refactoring plan?

Yes, you can generate a GitHub issue template. The Skill outputs an RFC-ready issue containing the problem statement, proposed changes, and testing considerations derived directly from your interview responses.

When do I need to break down refactoring changes into incremental steps?

You need to break down refactoring changes into incremental steps when facing major code restructuring that requires safe, auditable execution, ensuring each tiny commit remains independently testable throughout the process.

Does this refactoring plan tool require any external dependencies or components?

No external dependencies or components are required. The Skill operates independently to conduct the scoping interview and generate the incremental commit plan and RFC documentation.