Verified:GitHub

request-refactor-plan

Creates a refactor RFC with tiny incremental commits through structured user interviews.

2|Updated Apr 29, 2026

Search Tags:#code quality #planning #markdown #refactoring #technical debt #rfc #commit plan

One-click install

npx skills add https://github.com/siarhei-belavus/agent-public --skill request-refactor-plan-siarhei-belavus

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/siarhei-belavus/agent-public/tree/main/skills/planning/request-refactor-plan
Command: npx skills add https://github.com/siarhei-belavus/agent-public --skill request-refactor-plan-siarhei-belavus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Refactoring without a plan leads to oversized, risky changes that are hard to review and roll back. This Skill turns a vague refactor request into a concrete, low-risk RFC document with a step-by-step commit plan. ## Core Features & Use Cases - Structured Interview Process: Asks targeted questions about the problem, constraints, alternatives, scope, and testing strategy before writing anything. - Codebase Verification: Explores the repository to validate assumptions, identify dependencies, and assess test coverage in the affected area. - RFC Generation: Writes a markdown RFC to a local `.rfcs/` folder with sections for problem statement, goals, commit plan, decision record, and open questions. - Use Case: You want to split a monolithic service into modules. The Skill interviews you about boundaries and migration concerns, checks the code, then produces an RFC breaking the work into small, reviewable commits that each leave the system working. ## Quick Start Ask the assistant to plan a refactor of a specific module and save it as an RFC with a step-by-step 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 large refactor without breaking the codebase?▼

Break the refactor into tiny commits where each step leaves the system in a working state. This Skill interviews you about scope and constraints, checks test coverage, then writes an RFC with a detailed commit-by-commit plan.

How to write a refactoring RFC document?▼

A refactor RFC should include a problem statement, goals, non-goals, proposed approach, commit plan, decision record, and testing decisions. This Skill generates that structure as markdown in a local .rfcs/ folder with a kebab-case filename.

What should I check before starting a code refactor?▼

Verify test coverage in the affected area, understand dependencies and blast radius, and clarify what must not change. The Skill explores the repository to confirm these assumptions before drafting the plan.

When should I not use a formal refactor planning process?▼

Skip heavy planning for small, localized changes with obvious scope and strong existing test coverage. The interview-and-RFC workflow is designed for refactors with meaningful risk, unclear boundaries, or migration concerns.