request-refactor-plan

Original：🇨🇳 Chinese

Translated

Create a detailed refactor plan with tiny commits through user interviews, then file it as a GitHub issue. Use this when the user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

4installs

Sourcevinvcn/mattpocock-skills-zh-cn

Added on2026-05-28

NPX Install

npx skill4agent add vinvcn/mattpocock-skills-zh-cn request-refactor-plan

SKILL.md Content (Chinese)

View Translation Comparison →

Invoke this skill when the user wants to create a refactor request. Follow the steps below. You can skip any steps you deem unnecessary.

Ask the user to describe in detail the problem they want to solve, as well as possible solution ideas.
Explore the repo, verify their assertions, and understand the current state of the codebase.
Ask if they have considered other options, and present alternative options to them.
Interview the user about the implementation. Be extremely detailed and thorough.
Finalize the exact scope of the implementation. Clarify what you plan to change and what you will not change.
Check the test coverage of this area in the codebase. If coverage is insufficient, ask the user about their testing plans.
Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice: "make each refactoring step as small as possible, so that you can always see the program working."
Create a GitHub issue using the refactor plan. Use the template below for the issue description:

<refactor-plan-template>

Problem Statement

The problem faced by the developer, described from the developer's perspective.

Solution

The solution to the problem, described from the developer's perspective.

Commits

A long, detailed implementation plan. Write in plain English, breaking the implementation into the smallest possible commits. Each commit should leave the codebase in a working state.

Decision Document

A list of implementation decisions made. This can include:

Modules to be built/modified
Module interfaces to be modified
Technical clarifications from the developer
Architectural decisions
Schema changes
API contracts
Specific interactions

Do not include specific file paths or code snippets. They may become outdated quickly.

Testing Decisions

A list of testing decisions made. Include:

A description of what constitutes a good test (only test external behavior, not implementation details)
Which modules will be tested
Prior art for testing (i.e., similar types of tests in the codebase)

Out of Scope

A description of items outside the scope of this refactor.

Further Notes (optional)

Additional notes about the refactor.

</refactor-plan-template>