How do I install the Request Refactor Plan skill?

Run npx skillmds@latest add tomevault-io/request-refactor-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Request Refactor Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Request Refactor Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Request Refactor Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Request Refactor Plan?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Request Refactor Plan by tomevault-io

Name: Request Refactor Plan
Author: tomevault-io

Request Refactor Plan

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps. Use when this capability is needed.

tomevault-io 07852ae 2 files · 3.5 KB Updated Sep 17, 2026

File contents

This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.

Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Ask whether they have considered other options, and present other options to them.
Interview the user about the implementation. Be extremely detailed and thorough.
Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.
Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.
Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible, so that you can always see the program working."
Create a GitHub issue with the refactor plan. Use the following template for the issue description:

Problem Statement

The problem that the developer is facing, from the developer's perspective.

Solution

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

Commits

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

Decision Document

A list of implementation decisions that were made. This can include:

The modules that will be built/modified
The interfaces of those modules that will 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 end up being outdated very quickly.

Testing Decisions

A list of testing decisions that were made. Include:

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

Out of Scope

A description of the things that are out of scope for this refactor.

Further Notes (optional)

Any further notes about the refactor.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: request-refactor-plandescription: Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps. Use when this capability is needed.---This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.2. Explore the repo to verify their assertions and understand the current state of the codebase.3. Ask whether they have considered other options, and present other options to them.4. Interview the user about the implementation. Be extremely detailed and thorough.5. Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.6. Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.7. Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible, so that you can always see the program working."8. Create a GitHub issue with the refactor plan. Use the following template for the issue description:<refactor-plan-template>## Problem StatementThe problem that the developer is facing, from the developer's perspective.## SolutionThe solution to the problem, from the developer's perspective.## CommitsA LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.## Decision DocumentA list of implementation decisions that were made. This can include:- The modules that will be built/modified- The interfaces of those modules that will be modified- Technical clarifications from the developer- Architectural decisions- Schema changes- API contracts- Specific interactionsDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.## Testing DecisionsA list of testing decisions that were made. Include:- A description of what makes a good test (only test external behavior, not implementation details)- Which modules will be tested- Prior art for the tests (i.e. similar types of tests in the codebase)## Out of ScopeA description of the things that are out of scope for this refactor.## Further Notes (optional)Any further notes about the refactor.</refactor-plan-template>---> Converted and distributed by [TomeVault](https://tomevault.io/claim/mattpocock) — claim your Tome and manage your conversions.

Frequently asked questions