request-refactor-plan

Plan refactors into tiny commits with RFC and GitHub issue templates.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/caezium/skills --skill request-refactor-plan-caezium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/caezium/skills/tree/main/request-refactor-plan
Command: npx skills add https://github.com/caezium/skills --skill request-refactor-plan-caezium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This description explains how to plan a refactor by interviewing stakeholders, scoping changes, and documenting tiny, verifiable commits that can be filed as a GitHub issue.

Core Features & Use Cases

  • Structured interview steps to extract goals, constraints, and success criteria for a refactor.
  • Step-by-step plan drafting that breaks the work into tiny commits and an RFC template.
  • GitHub issue generation with a complete refactor plan, acceptance criteria, and testing considerations.

Quick Start

Describe the refactor goal and constraints, and let this skill generate a tiny-commit plan and an RFC-formatted GitHub issue.

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 code refactor with incremental changes?

Plan a code refactor with incremental changes by guiding stakeholders through structured interviews to extract scope, define tiny verifiable commits, and produce a ready-to-file RFC document.

What is the best way to break down a large software project into tiny commits?

Break down a large software project into tiny commits using structured interview steps to extract goals, assess test coverage, and draft step-by-step plans that generate a complete GitHub issue template.

How do I prepare an RFC for a software project refactor?

Prepare an RFC for a software project refactor by documenting stakeholder constraints, success criteria, and testing considerations into a formatted RFC template ready for GitHub issue creation.

Can I generate a GitHub issue template for a refactor plan?

Generate a GitHub issue template for a refactor plan by defining acceptance criteria and testing considerations during the scoping phase, which produces an issue template formatted for direct filing.

Does planning a refactor require stakeholder interviews?

Planning a refactor does require stakeholder interviews to accurately extract project goals, constraints, and success criteria before defining the incremental changes and drafting the RFC documentation.

When should I not use a tiny commit strategy for refactoring?

Avoid a tiny commit strategy for refactoring when a software project lacks sufficient test coverage to verify each incremental change, or when stakeholder constraints prevent structured scoping interviews.